Radio link monitoring (RLM) for unicast sidelink (SL) communications

ABSTRACT

Apparatuses, systems, and methods are disclosed for radio link monitoring (RLM) for unicast sidelink (SL) communications. A processor for a base station includes first circuitry configured to generate a radio resource control (RRC) message comprising an RRC information element indicating a number of unicast SL RLM reference signals. The processor includes second circuitry configured to encode the RRC message for transmission to a user equipment (UE). The processor includes third circuitry configured to generate a reference signal indicating an in-sync (IS) threshold and an out-of-sync (OOS) threshold for an RLM resource. The processor includes fourth circuitry configured to encode the reference signal for transmission to the UE. The processor includes fifth circuitry configured to transmit the RRC message and the reference signal to the UE.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority from U.S. Provisional Application No.62/872,634 filed on Jul. 10, 2019, which is incorporated by reference inits entirety herein.

TECHNICAL FIELD

This description relates generally to wireless devices, and moreparticularly to apparatus, systems, and methods for radio linkmonitoring (RLM) for unicast sidelink (SL) communications.

BACKGROUND

Wireless communication systems are rapidly growing in use. Further,wireless communication technology has evolved from voice-onlycommunications to also include the transmission of data, such asInternet and multimedia content. However, the radio link failure (RLF)procedure in the air interface physical layer (Uu interface) can posechallenges when link conditions between a user equipment (UE) and aserving cell deteriorate. The access stratum can indicate thedeteriorating link conditions to the upper layer (e.g., “out-of-sync”(OOS)), and an RLF is declared if the link conditions stay poor for acertain time period. Moreover, RLF can also be triggered by randomaccess problems or when a maximum number of radio link control (RLC)retransmissions are reached.

SUMMARY

The implementations disclosed provide apparatus, systems, and methodsfor radio link monitoring (RLM) for unicast sidelink (SL)communications. A processor for a base station includes first circuitryconfigured to generate a radio resource control (RRC) message comprisingan RRC information element indicating a number of unicast SL RLMreference signals. The processor includes second circuitry configured toencode the RRC message for transmission to a user equipment (UE). Theprocessor includes third circuitry configured to generate a referencesignal indicating an in-sync (IS) threshold and an out-of-sync (OOS)threshold for an RLM resource. The processor includes fourth circuitryconfigured to encode the reference signal for transmission to the UE.The processor includes fifth circuitry configured to transmit the RRCmessage and the reference signal to the UE.

In some implementations, the RRC information element further indicates atype of the RLM resource.

In some implementations, the RRC information element further indicates atimer and a constant for at least one of a radio link failure (RLF)detection procedure or a unicast SL connection procedure.

In some implementations, the RRC information element further indicatesan IS/OOS threshold configuration based on the IS threshold and the OOSthreshold for the RLM resource.

In some implementations, the reference signal is a channel stateinformation-reference signal (CSI-RS) or a demodulation reference signal(DMRS).

In some implementations, the reference signal further indicates a numberof consecutive reception events for an IS determination.

In some implementations, the reference signal further indicates a numberof consecutive erroneous reception events required for an OOSdetermination.

The implementations disclosed herein enable RLM/RLF functions forunicast SL communications. Among others, the advantages and benefits ofthe implementations disclosed include support for both TX-side andRX-side RLM using generic RLM detection resources. RLF detectioncriteria can be semi-statically configured using RRC signaling. Theunicast SL RB link connection can be released, resumed, or recoveredusing timer operations. As a result, RLM/RLF and associated unicast SLmanagement is supported in a resource efficient manner. Theimplementations further enable SL radio resource management (RRM)-basedAS-level link management and RLM reference signal (RS) design inaccordance with 3GPP RAN 1. In accordance with 3GPP RAN2, the airinterface physical layer (Uu) RLM model is supported for SL RLM.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a wireless communication system, inaccordance with one or more implementations.

FIG. 2 illustrates an example architecture of a system including a firstcore network (CN), in accordance with one or more implementations.

FIG. 3 illustrates an architecture of a system including a second CN, inaccordance with one or more implementations.

FIG. 4 illustrates an example of infrastructure equipment in accordancewith one or more implementations.

FIG. 5 illustrates an example of a platform (or “device”) in accordancewith one or more implementations.

FIG. 6 illustrates example components of baseband circuitry and radiofront end modules (RFEM) in accordance with one or more implementations.

FIG. 7 illustrates various protocol functions that can be implemented ina wireless communication device according to one or moreimplementations.

FIG. 8 illustrates components of a core network in accordance with oneor more implementations.

FIG. 9 is a block diagram illustrating components, according to someexample implementations, of a system 900 to support Network FunctionsVirtualization (NFV).

FIG. 10 is a block diagram illustrating components, according to someexample implementations, able to read instructions from amachine-readable or computer-readable medium (e.g., a non-transitorymachine-readable storage medium) and perform any one or more of themethodologies discussed herein.

FIG. 11 is a block diagram illustrating an example of radio linkmonitoring (RLM)-based unicast sidelink (SL) management, according toone or more implementations.

FIG. 12 is a block diagram illustrating an example of RLM-based unicastSL management with SL recovery, according to one or moreimplementations.

FIG. 13 is a flowchart illustrating a process for RLM monitoring forunicast SL communications.

DETAILED DESCRIPTION

In the air interface physical layer (Uu interface), the radio linkfailure (RLF) procedure can pose challenges when link conditions betweena user equipment (UE) and a serving cell deteriorate. The access stratumcan indicate the deteriorating link conditions to the upper layer (e.g.,“out-of-sync” (OOS)), and an RLF is declared if the link conditions staypoor for a certain time period. Moreover, RLF can also be triggered byrandom access problems or when a maximum number of radio link control(RLC) retransmissions are reached.

The implementations disclosed provide apparatus, systems, and methodsfor radio link monitoring (RLM) for unicast sidelink (SL)communications. The implementations enable a UE to recover a link viaradio resource control (RRC) re-establishment after an RLF is declared.For SL unicast link management, continuous evaluation by the UE of analready established link with another peer UE is enabled; moreover, theUE is enabled to react once the link conditions deteriorate. Theimplementations support the 3GPP RAN2 agreement that both radio resourcemanagement (RRM) and RLM-based solutions can be used for access stratum(AS)-level link management for NR SL unicast.

In some implementations, a processor for a base station includes firstcircuitry configured to generate a radio resource control (RRC) messagecomprising an RRC information element indicating a number of unicast SLRLM reference signals. The processor includes second circuitryconfigured to encode the RRC message for transmission to a userequipment (UE). The processor includes third circuitry configured togenerate a reference signal indicating an in-sync (IS) threshold and anout-of-sync (OOS) threshold for an RLM resource. The processor includesfourth circuitry configured to encode the reference signal fortransmission to the UE. The processor includes fifth circuitryconfigured to transmit the RRC message and the reference signal to theUE.

FIG. 1 illustrates an example of a wireless communication system 100.For purposes of convenience and without limitation, the example system100 is described in the context of Long Term Evolution (LTE) and FifthGeneration (5G) New Radio (NR) communication standards as defined by theThird Generation Partnership Project (3GPP) technical specifications.More specifically, the wireless communication system 100 is described inthe context of a Non-Standalone (NSA) networks that incorporate both LTEand NR, for example, E-UTRA (Evolved Universal Terrestrial RadioAccess)-NR Dual Connectivity (EN-DC) networks, and NE-DC networks.However, the wireless communication system 100 can also be a Standalone(SA) network that incorporates only NR. Furthermore, other types ofcommunication standards are possible, including future 3GPP systems(e.g., Sixth Generation (6G)) systems, IEEE 802.16 protocols (e.g.,WMAN, WiMAX, etc.), or the like.

As shown by FIG. 1, the system 100 includes UE 101 a and UE 101 b(collectively referred to as “UEs 101” or “UE 101”). In this example,UEs 101 are illustrated as smartphones (e.g., handheld touchscreenmobile computing devices connectable to one or more cellular networks),but can also include any mobile or non-mobile computing device, such asconsumer electronics devices, cellular phones, smartphones, featurephones, tablet computers, wearable computer devices, personal digitalassistants (PDAs), pagers, wireless handsets, desktop computers, laptopcomputers, in-vehicle infotainment (IVI), in-car entertainment (ICE)devices, an Instrument Cluster (IC), head-up display (HUD) devices,onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobiledata terminals (MDTs), Electronic Engine Management System (EEMS),electronic/engine control units (ECUs), electronic/engine controlmodules (ECMs), embedded systems, microcontrollers, control modules,engine management systems (EMS), networked or “smart” appliances, MTCdevices, M2M, IoT devices, and/or the like.

In some implementations, any of the UEs 101 can be IoT UEs, which caninclude a network access layer designed for low-power IoT applicationsutilizing short-lived UE connections. An IoT UE can utilize technologiessuch as M2M or MTC for exchanging data with an MTC server or device viaa PLMN, ProSe or D2D communication, sensor networks, or IoT networks.The M2M or MTC exchange of data can be a machine-initiated exchange ofdata. An IoT network describes interconnecting IoT UEs, which caninclude uniquely identifiable embedded computing devices (within theInternet infrastructure), with short-lived connections. The IoT UEs canexecute background applications (e.g., keep-alive messages, statusupdates, etc.) to facilitate the connections of the IoT network.

The UEs 101 can be configured to connect, for example, communicativelycouple, with RAN 110. In implementations, the RAN 110 can be an NG RANor a 5G RAN, an E-UTRAN, or a legacy RAN, such as a UTRAN or GERAN. Asused herein, the term “NG RAN” or the like can refer to a RAN 110 thatoperates in an NR or 5G system 100, and the term “E-UTRAN” or the likecan refer to a RAN 110 that operates in an LTE or 4G system 100. The UEs101 utilize connections (or channels) 103 and 104, respectively, each ofwhich includes a physical communications interface or layer (discussedin further detail below).

In this example, the connections 103 and 104 are illustrated as an airinterface to enable communicative coupling, and can be consistent withcellular communications protocols, such as a GSM protocol, a CDMAnetwork protocol, a PTT protocol, a POC protocol, a UMTS protocol, a3GPP LTE protocol, an Advanced long term evolution (LTE-A) protocol, aLTE-based access to unlicensed spectrum (LTE-U), a 5G protocol, a NRprotocol, an NR-based access to unlicensed spectrum (NR-U) protocol,and/or any of the other communications protocols discussed herein. Inimplementations, the UEs 101 can directly exchange communication datavia a ProSe interface 105. The ProSe interface 105 can alternatively bereferred to as a SL interface 105 and can include one or more logicalchannels, including but not limited to a PSCCH, a PSSCH, a PSDCH, and aPSBCH.

The UE 101 b is shown to be configured to access an AP 106 (alsoreferred to as “WLAN node 106,” “WLAN 106,” “WLAN Termination 106,” “WT106” or the like) via connection 107. The connection 107 can include alocal wireless connection, such as a connection consistent with any IEEE802.11 protocol, wherein the AP 106 would include a wireless fidelity(Wi-Fi®) router. In this example, the AP 106 is shown to be connected tothe Internet without connecting to the core network of the wirelesssystem (described in further detail below). In various implementations,the UE 101 b, RAN 110, and AP 106 can be configured to utilize LWAoperation and/or LWIP operation. The LWA operation can involve the UE101 b in RRC_CONNECTED being configured by a RAN node 111 a-b to utilizeradio resources of LTE and WLAN. LWIP operation can involve the UE 101 busing WLAN radio resources (e.g., connection 107) via IPsec protocoltunneling to authenticate and encrypt packets (e.g., IP packets) sentover the connection 107. IPsec tunneling can include encapsulating theentirety of original IP packets and adding a new packet header, therebyprotecting the original header of the IP packets.

The RAN 110 can include one or more AN nodes or RAN nodes 111 a and 111b (collectively referred to as “RAN nodes 111” or “RAN node 111”) thatenable the connections 103 and 104. As used herein, the terms “accessnode,” “access point,” or the like can describe equipment that providesthe radio baseband functions for data and/or voice connectivity betweena network and one or more users. These access nodes can be referred toas base station (BS), gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs orTRPs, and so forth, and can include ground stations (e.g., terrestrialaccess points) or satellite stations providing coverage within ageographic area (e.g., a cell). As used herein, the term “NG RAN node”or the like can refer to a RAN node 111 that operates in an NR or 5Gsystem 100 (for example, a gNB), and the term “E-UTRAN node” or the likecan refer to a RAN node 111 that operates in an LTE or 4G system 100(e.g., an eNB). According to various implementations, the RAN nodes 111can be implemented as one or more of a dedicated physical device such asa macrocell base station, and/or a low power (LP) base station forproviding femtocells, picocells or other like cells having smallercoverage areas, smaller user capacity, or higher bandwidth compared tomacrocells.

In some implementations, all or parts of the RAN nodes 111 can beimplemented as one or more software entities running on server computersas part of a virtual network, which can be referred to as a CRAN and/ora virtual baseband unit pool (vBBUP). In these implementations, the CRANor vBBUP can implement a RAN function split, such as a PDCP splitwherein RRC and PDCP layers are operated by the CRAN/vBBUP and other L2protocol entities are operated by individual RAN nodes 111; a MAC/PHYsplit wherein RRC, PDCP, RLC, and MAC layers are operated by theCRAN/vBBUP and the PHY layer is operated by individual RAN nodes 111; ora “lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upperportions of the PHY layer are operated by the CRAN/vBBUP and lowerportions of the PHY layer are operated by individual RAN nodes 111. Thisvirtualized framework allows the freed-up processor cores of the RANnodes 111 to perform other virtualized applications. In someimplementations, an individual RAN node 111 can represent individualgNB-DUs that are connected to a gNB-CU via individual F1 interfaces (notshown by FIG. 1). In these implementations, the gNB-DUs can include oneor more remote radio heads or RFEMs (see, e.g., FIG. 4), and the gNB-CUcan be operated by a server that is located in the RAN 110 (not shown)or by a server pool in a similar manner as the CRAN/vBBUP. Additionallyor alternatively, one or more of the RAN nodes 111 can be nextgeneration eNBs (ng-eNBs), which are RAN nodes that provide E-UTRA userplane and control plane protocol terminations toward the UEs 101, andare connected to a 5GC (e.g., CN 320 of FIG. 3) via an NG interface(discussed infra).

In V2X scenarios one or more of the RAN nodes 111 can be or act as RSUs.The term “Road Side Unit” or “RSU” can refer to any transportationinfrastructure entity used for V2X communications. An RSU can beimplemented in or by a suitable RAN node or a stationary (or relativelystationary) UE, where an RSU implemented in or by a UE can be referredto as a “UE-type RSU,” an RSU implemented in or by an eNB can bereferred to as an “eNB-type RSU,” an RSU implemented in or by a gNB canbe referred to as a “gNB-type RSU,” and the like. In one example, an RSUis a computing device coupled with radio frequency circuitry located ona roadside that provides connectivity support to passing vehicle UEs 101(vUEs 101). The RSU can also include internal data storage circuitry tostore intersection map geometry, traffic statistics, media, as well asapplications/software to detect and control ongoing vehicular andpedestrian traffic. The RSU can operate on the 5.9 GHz Direct ShortRange Communications (DSRC) band to provide very low latencycommunications required for high speed events, such as crash avoidance,traffic warnings, and the like. Additionally or alternatively, the RSUcan operate on the cellular V2X band to provide the aforementioned lowlatency communications, as well as other cellular communicationsservices. Additionally or alternatively, the RSU can operate as a Wi-Fihotspot (2.4 GHz band) and/or provide connectivity to one or morecellular networks to provide uplink and downlink communications. Thecomputing device(s) and some or all of the radiofrequency circuitry ofthe RSU can be packaged in a weatherproof enclosure suitable for outdoorinstallation, and can include a network interface controller to providea wired connection (e.g., Ethernet) to a traffic signal controllerand/or a backhaul network.

Any of the RAN nodes 111 can terminate the air interface protocol andcan be the first point of contact for the UEs 101. In someimplementations, any of the RAN nodes 111 can fulfill various logicalfunctions for the RAN 110 including, but not limited to, radio networkcontroller (RNC) functions such as radio bearer management, uplink anddownlink dynamic radio resource management and data packet scheduling,and mobility management.

In implementations, the UEs 101 can be configured to communicate usingOFDM communication signals with each other or with any of the RAN nodes111 over a multicarrier communication channel. The UEs 101 cancommunicate in accordance with various communication techniques, suchas, but not limited to, an OFDMA communication technique (e.g., fordownlink communications) or a SC-FDMA communication technique (e.g., foruplink and ProSe or sidelink communications). However, the scope of theimplementations is not limited in this respect. The OFDM signals caninclude multiple orthogonal subcarriers.

In some implementations, a downlink resource grid can use downlinktransmissions from any of the RAN nodes 111 to the UEs 101, while uplinktransmissions can utilize similar techniques. The grid can be atime-frequency grid, called a resource grid or time-frequency resourcegrid, which is the physical resource in the downlink in each slot. Sucha time-frequency plane representation is a common practice for OFDMsystems, which makes it intuitive for radio resource allocation. Eachcolumn and each row of the resource grid corresponds to one OFDM symboland one OFDM subcarrier, respectively. The duration of the resource gridin the time domain corresponds to one slot in a radio frame. A smallertime-frequency unit in a resource grid is a resource element. Eachresource grid includes a number of resource blocks, which describe themapping of certain physical channels to resource elements. Each resourceblock includes a collection of resource elements; in the frequencydomain, this can represent a smaller quantity of resources thatcurrently can be allocated. There are several different physicaldownlink channels that are conveyed using such resource blocks.

According to various implementations, the UEs 101 and the RAN nodes 111communicate data (for example, transmit and receive) data over alicensed medium (also referred to as the “licensed spectrum” and/or the“licensed band”) and an unlicensed shared medium (also referred to asthe “unlicensed spectrum” and/or the “unlicensed band”). The licensedspectrum can include channels that operate in the frequency range ofapproximately 400 MHz to approximately 3.8 GHz, whereas the unlicensedspectrum can include the 5 GHz band. NR in the unlicensed spectrum canbe referred to as NR-U, and LTE in an unlicensed spectrum can bereferred to as LTE-U, licensed assisted access (LAA), or MulteFire.

To operate in the unlicensed spectrum, the UEs 101 and the RAN nodes 111can operate using LAA, eLAA, and/or feLAA mechanisms. In theseimplementations, the UEs 101 and the RAN nodes 111 can perform one ormore known medium-detecting operations and/or carrier-detectingoperations in order to determine whether one or more channels in theunlicensed spectrum is unavailable or otherwise occupied prior totransmitting in the unlicensed spectrum. The medium/carrier detectingoperations can be performed according to a listen-before-talk (LBT)protocol.

LBT is a mechanism whereby equipment (for example, UEs 101 RAN nodes111, etc.) detects a medium (for example, a channel or carrierfrequency) and transmits when the medium is idle (or when a specificchannel in the medium is unoccupied). The medium detecting operation caninclude CCA, which utilizes at least ED to determine the presence orabsence of other signals on a channel in order to determine if a channelis occupied or clear. This LBT mechanism allows cellular/LAA networks tocoexist with incumbent systems in the unlicensed spectrum and with otherLAA networks. ED can include detecting RF energy across an intendedtransmission band for a period of time and comparing the RF energy to apredefined or configured threshold.

Typically, the incumbent systems in the 5 GHz band are WLANs based onIEEE 802.11 technologies. WLAN employs a contention-based channel accessmechanism, called CSMA/CA. Here, when a WLAN node (e.g., a mobilestation (MS) such as UE 101, AP 106, or the like) intends to transmit,the WLAN node can first perform CCA before transmission. Additionally, abackoff mechanism is used to avoid collisions in situations where morethan one WLAN node detects the channel as idle and transmits at the sametime. The backoff mechanism can be a counter that is drawn randomlywithin the CWS, which is increased exponentially upon the occurrence ofcollision and reset to a smaller value when the transmission succeeds.The LBT mechanism designed for LAA is somewhat similar to the CSMA/CA ofWLAN. In some implementations, the LBT procedure for DL or ULtransmission bursts including PDSCH or PUSCH transmissions,respectively, can have an LAA contention window that is variable inlength between X and Y ECCA slots, where X and Y are smaller and largervalues for the CWSs for LAA. In one example, a smaller CWS for an LAAtransmission can be 9 microseconds (s); however, the size of the CWS anda MCOT (for example, a transmission burst) can be based on governmentalregulatory requirements.

The LAA mechanisms are built upon CA technologies of LTE-Advancedsystems. In CA, each aggregated carrier is referred to as a CC. A CC canhave a bandwidth of 1.4, 3, 5, 10, 15 or 20 MHz and five CCs can beaggregated, and therefore, an aggregated bandwidth is 100 MHz. In FDDsystems, the number of aggregated carriers can be different for DL andUL, where the number of UL CCs is equal to or lower than the number ofDL component carriers. In some cases, individual CCs can have adifferent bandwidth than other CCs. In TDD systems, the number of CCs aswell as the bandwidths of each CC is usually the same for DL and UL.

CA also includes individual serving cells to provide individual CCs. Thecoverage of the serving cells can differ, for example, because CCs ondifferent frequency bands will experience different pathloss. A primaryservice cell or PCell can provide a PCC for both UL and DL, and canhandle RRC and NAS related activities. The other serving cells arereferred to as SCells, and each SCell can provide an individual SCC forboth UL and DL. The SCCs can be added and removed as required, whilechanging the PCC can require the UE 101 to undergo a handover. In LAA,eLAA, and feLAA, some or all of the SCells can operate in the unlicensedspectrum (referred to as “LAA SCells”), and the LAA SCells are assistedby a PCell operating in the licensed spectrum. When a UE is configuredwith more than one LAA SCell, the UE can receive UL grants on theconfigured LAA SCells indicating different PUSCH starting positionswithin a same subframe.

The PDSCH carries user data and higher-layer signaling to the UEs 101.The PDCCH carries information about the transport format and resourceallocations related to the PDSCH channel, among other things. It canalso inform the UEs 101 about the transport format, resource allocation,and HARQ information related to the uplink shared channel. Typically,downlink scheduling (assigning control and shared channel resourceblocks to the UE 101 b within a cell) can be performed at any of the RANnodes 111 based on channel quality information fed back from any of theUEs 101. The downlink resource assignment information can be sent on thePDCCH used for (e.g., assigned to) each of the UEs 101.

The PDCCH uses CCEs to convey the control information. Before beingmapped to resource elements, the PDCCH complex-valued symbols can firstbe organized into quadruplets, which can then be permuted using asub-block interleaver for rate matching. Each PDCCH can be transmittedusing one or more of these CCEs, where each CCE can correspond to ninesets of four physical resource elements known as REGs. Four QuadraturePhase Shift Keying (QPSK) symbols can be mapped to each REG. The PDCCHcan be transmitted using one or more CCEs, depending on the size of theDCI and the channel condition. There can be four or more different PDCCHformats defined in LTE with different numbers of CCEs (e.g., aggregationlevel, L=1, 2, 4, or 8).

Some implementations can use concepts for resource allocation forcontrol channel information that are an extension of the above-describedconcepts. For example, some implementations can utilize an EPDCCH thatuses PDSCH resources for control information transmission. The EPDCCHcan be transmitted using one or more ECCEs. Similar to above, each ECCEcan correspond to nine sets of four physical resource elements known asan EREGs. An ECCE can have other numbers of EREGs in some situations.

The RAN nodes 111 can be configured to communicate with one another viainterface 112. In implementations where the system 100 is an LTE system(e.g., when CN 120 is an EPC 220 as in FIG. 2), the interface 112 can bean X2 interface 112. The X2 interface can be defined between two or moreRAN nodes 111 (e.g., two or more eNBs and the like) that connect to EPC120, and/or between two eNBs connecting to EPC 120. In someimplementations, the X2 interface can include an X2 user plane interface(X2-U) and an X2 control plane interface (X2-C). The X2-U can provideflow control mechanisms for user data packets transferred over the X2interface, and can be used to communicate information about the deliveryof user data between eNBs. For example, the X2-U can provide specificsequence number information for user data transferred from a MeNB to anSeNB; information about successful in sequence delivery of PDCP PDUs toa UE 101 from an SeNB for user data; information of PDCP PDUs that werenot delivered to a UE 101; information about a current smaller desiredbuffer size at the SeNB for transmitting to the UE user data; and thelike. The X2-C can provide intra-LTE access mobility functionality,including context transfers from source to target eNBs, user planetransport control, etc.; load management functionality; as well asinter-cell interference coordination functionality.

In implementations where the system 100 is a 5G or NR system (e.g., whenCN 120 is an 5GC 320 as in FIG. 3), the interface 112 can be an Xninterface 112. The Xn interface is defined between two or more RAN nodes111 (e.g., two or more gNBs and the like) that connect to 5GC 120,between a RAN node 111 (e.g., a gNB) connecting to 5GC 120 and an eNB,and/or between two eNBs connecting to 5GC 120. In some implementations,the Xn interface can include an Xn user plane (Xn-U) interface and an Xncontrol plane (Xn-C) interface. The Xn-U can provide non-guaranteeddelivery of user plane PDUs and support/provide data forwarding and flowcontrol functionality. The Xn-C can provide management and errorhandling functionality, functionality to manage the Xn-C interface;mobility support for UE 101 in a connected mode (e.g., CM-CONNECTED)including functionality to manage the UE mobility for connected modebetween one or more RAN nodes 111. The mobility support can includecontext transfer from an old (source) serving RAN node 111 to new(target) serving RAN node 111; and control of user plane tunnels betweenold (source) serving RAN node 111 to new (target) serving RAN node 111.A protocol stack of the Xn-U can include a transport network layer builton Internet Protocol (IP) transport layer, and a GTP-U layer on top of aUDP and/or IP layer(s) to carry user plane PDUs. The Xn-C protocol stackcan include an application layer signaling protocol (referred to as XnApplication Protocol (Xn-AP)) and a transport network layer that isbuilt on SCTP. The SCTP can be on top of an IP layer, and can providethe guaranteed delivery of application layer messages. In the transportIP layer, point-to-point transmission is used to deliver the signalingPDUs. In other implementations, the Xn-U protocol stack and/or the Xn-Cprotocol stack can be same or similar to the user plane and/or controlplane protocol stack(s) shown and described herein.

The RAN 110 is shown to be communicatively coupled to a core network—inthis implementation, core network (CN) 120. The CN 120 can includemultiple network elements 122, which are configured to offer variousdata and telecommunications services to customers/subscribers (e.g.,users of UEs 101) who are connected to the CN 120 via the RAN 110. Thecomponents of the CN 120 can be implemented in one physical node orseparate physical nodes including components to read and executeinstructions from a machine-readable or computer-readable medium (e.g.,a non-transitory machine-readable storage medium). In someimplementations, NFV can be utilized to virtualize any or all of theabove-described network node functions via executable instructionsstored in one or more computer-readable storage mediums (described infurther detail below). A logical instantiation of the CN 120 can bereferred to as a network slice, and a logical instantiation of a portionof the CN 120 can be referred to as a network sub-slice. NFVarchitectures and infrastructures can be used to virtualize one or morenetwork functions, alternatively performed by proprietary hardware, ontophysical resources including a combination of industry-standard serverhardware, storage hardware, or switches. In other words, NFV systems canexecute virtual or reconfigurable implementations of one or more EPCcomponents/functions.

Generally, the application server 130 can be an element offeringapplications that use IP bearer resources with the core network (e.g.,UMTS PS domain, LTE PS data services, etc.). The application server 130can also be configured to support one or more communication services(e.g., VoIP sessions, PTT sessions, group communication sessions, socialnetworking services, etc.) for the UEs 101 via the EPC 120.

In implementations, the CN 120 can be a 5GC (referred to as “5GC 120” orthe like), and the RAN 110 can be connected with the CN 120 via an NGinterface 113. In implementations, the NG interface 113 can be splitinto two parts, an NG user plane (NG-U) interface 114, which carriestraffic data between the RAN nodes 111 and a UPF, and the S1 controlplane (NG-C) interface 115, which is a signaling interface between theRAN nodes 111 and AMFs. Implementations where the CN 120 is a 5GC 120are discussed in more detail with regard to FIG. 3.

In implementations, the CN 120 can be a 5G CN (referred to as “5GC 120”or the like), while in other implementations, the CN 120 can be an EPC).Where CN 120 is an EPC (referred to as “EPC 120” or the like), the RAN110 can be connected with the CN 120 via an S1 interface 113. Inimplementations, the S1 interface 113 can be split into two parts, an S1user plane (S1-U) interface 114, which carries traffic data between theRAN nodes 111 and the S-GW, and the S1-MME interface 115, which is asignaling interface between the RAN nodes 111 and MMES.

FIG. 2 illustrates an example architecture of a system 200 including afirst CN 220, in accordance with one or more implementations. In thisexample, system 200 can implement the LTE standard wherein the CN 220 isan EPC 220 that corresponds with CN 120 of FIG. 1. Additionally, the UE201 can be the same or similar as the UEs 101 of FIG. 1, and the E-UTRAN210 can be a RAN that is the same or similar to the RAN 110 of FIG. 1,and which can include RAN nodes 111 discussed previously. The CN 220 caninclude MMEs 221, an S-GW 222, a P-GW 223, a HSS 224, and a SGSN 225.

The MMEs 221 can be similar in function to the control plane of legacySGSN, and can implement MM functions to keep track of the currentlocation of a UE 201. The MMEs 221 can perform various MM procedures tomanage mobility aspects in access such as gateway selection and trackingarea list management. MM (also referred to as “EPS MM” or “EMM” inE-UTRAN systems) can refer to all applicable procedures, methods, datastorage, etc. That are used to maintain knowledge about a presentlocation of the UE 201, provide user identity confidentiality, and/orperform other like services to users/subscribers. Each UE 201 and theMME 221 can include an MM or EMM sublayer, and an MM context can beestablished in the UE 201 and the MME 221 when an attach procedure issuccessfully completed. The MM context can be a data structure ordatabase object that stores MM-related information of the UE 201. TheMMEs 221 can be coupled with the HSS 224 via an S6a reference point,coupled with the SGSN 225 via an S3 reference point, and coupled withthe S-GW 222 via an S11 reference point.

The SGSN 225 can be a node that serves the UE 201 by tracking thelocation of an individual UE 201 and performing security functions. Inaddition, the SGSN 225 can perform Inter-EPC node signaling for mobilitybetween 2G/3G and E-UTRAN 3GPP access networks; PDN and S-GW selectionas specified by the MMEs 221; handling of UE 201 time zone functions asspecified by the MMEs 221; and MME selection for handovers to E-UTRAN3GPP access network. The S3 reference point between the MMEs 221 and theSGSN 225 can enable user and bearer information exchange for inter-3GPPaccess network mobility in idle and/or active states.

The HSS 224 can include a database for network users, includingsubscription-related information to support the network entities'handling of communication sessions. The EPC 220 can include one orseveral HSSs 224, depending on the number of mobile subscribers, on thecapacity of the equipment, on the organization of the network, etc. Forexample, the HSS 224 can provide support for routing/roaming,authentication, authorization, naming/addressing resolution, locationdependencies, etc. An S6a reference point between the HSS 224 and theMMEs 221 can enable transfer of subscription and authentication data forauthenticating/authorizing user access to the EPC 220 between HSS 224and the MMEs 221.

The S-GW 222 can terminate the S1 interface 113 (“S1-U” in FIG. 2)toward the RAN 210, and routes data packets between the RAN 210 and theEPC 220. In addition, the S-GW 222 can be a local mobility anchor pointfor inter-RAN node handovers and also can provide an anchor forinter-3GPP mobility. Other responsibilities can include lawfulintercept, charging, and some policy enforcement. The S11 referencepoint between the S-GW 222 and the MMEs 221 can provide a control planebetween the MMEs 221 and the S-GW 222. The S-GW 222 can be coupled withthe P-GW 223 via an S5 reference point.

The P-GW 223 can terminate an SGi interface toward a PDN 230. The P-GW223 can route data packets between the EPC 220 and external networkssuch as a network including the application server 130 (alternativelyreferred to as an “AF”) via an IP interface 125 (see e.g., FIG. 1). Inimplementations, the P-GW 223 can be communicatively coupled to anapplication server (application server 130 of FIG. 1 or PDN 230 in FIG.2) via an IP communications interface 125 (see, e.g., FIG. 1). The S5reference point between the P-GW 223 and the S-GW 222 can provide userplane tunneling and tunnel management between the P-GW 223 and the S-GW222. The S5 reference point can also be used for S-GW 222 relocation dueto UE 201 mobility and if the S-GW 222 needs to connect to anon-collocated P-GW 223 for the required PDN connectivity. The P-GW 223can further include a node for policy enforcement and charging datacollection (e.g., PCEF (not shown)). Additionally, the SGi referencepoint between the P-GW 223 and the packet data network (PDN) 230 can bean operator external public, a private PDN, or an intra operator packetdata network, for example, for provision of IMS services. The P-GW 223can be coupled with a PCRF 226 via a Gx reference point.

PCRF 226 is the policy and charging control element of the EPC 220. In anon-roaming scenario, there can be a single PCRF 226 in the Home PublicLand Mobile Network (HPLMN) associated with a UE 201's Internet ProtocolConnectivity Access Network (IP-CAN) session. In a roaming scenario withlocal breakout of traffic, there can be two PCRFs associated with a UE201's IP-CAN session, a Home PCRF (H-PCRF) within an HPLMN and a VisitedPCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). ThePCRF 226 can be communicatively coupled to the application server 230via the P-GW 223. The application server 230 can signal the PCRF 226 toindicate a new service flow and select the appropriate QoS and chargingparameters. The PCRF 226 can provision this rule into a PCEF (not shown)with the appropriate TFT and QCI, which commences the QoS and chargingas specified by the application server 230. The Gx reference pointbetween the PCRF 226 and the P-GW 223 can allow for the transfer of QoSpolicy and charging rules from the PCRF 226 to PCEF in the P-GW 223. AnRx reference point can reside between the PDN 230 (or “AF 230”) and thePCRF 226.

FIG. 3 illustrates an architecture of a system 300 including a second CN320, in accordance with one or more implementations. The system 300 isshown to include a UE 301, which can be the same or similar to the UEs101 and UE 201 discussed previously; a (R)AN 310, which can be the sameor similar to the RAN 110 and RAN 210 discussed previously, and whichcan include RAN nodes 111 discussed previously; and a DN 303, which canbe, for example, operator services, Internet access or 3rd partyservices; and a 5GC 320. The 5GC 320 can include an AUSF 322; an AMF321; a SMF 324; a NEF 323; a PCF 326; a NRF 325; a UDM 327; an AF 328; aUPF 302; and a NSSF 329.

The UPF 302 can act as an anchor point for intra-RAT and inter-RATmobility, an external PDU session point of interconnect to DN 303, and abranching point to support multi-homed PDU session. The UPF 302 can alsoperform packet routing and forwarding, perform packet inspection,enforce the user plane part of policy rules, lawfully intercept packets(UP collection), perform traffic usage reporting, perform QoS handlingfor a user plane (e.g., packet filtering, gating, UL/DL rateenforcement), perform Uplink Traffic verification (e.g., SDF to QoS flowmapping), transport level packet marking in the uplink and downlink, andperform downlink packet buffering and downlink data notificationtriggering. UPF 302 can include an uplink classifier to support routingtraffic flows to a data network. The DN 303 can represent variousnetwork operator services, Internet access, or third party services. DN303 can include, or be similar to, application server 130 discussedpreviously. The UPF 302 can interact with the SMF 324 via an N4reference point between the SMF 324 and the UPF 302.

The AUSF 322 can store data for authentication of UE 301 and handleauthentication-related functionality. The AUSF 322 can facilitate acommon authentication framework for various access types. The AUSF 322can communicate with the AMF 321 via an N12 reference point between theAMF 321 and the AUSF 322; and can communicate with the UDM 327 via anN13 reference point between the UDM 327 and the AUSF 322. Additionally,the AUSF 322 can exhibit an Nausf service-based interface.

The AMF 321 can be responsible for registration management (e.g., forregistering UE 301, etc.), connection management, reachabilitymanagement, mobility management, and lawful interception of AMF-relatedevents, and access authentication and authorization. The AMF 321 can bea termination point for the N11 reference point between the AMF 321 andthe SMF 324. The AMF 321 can provide transport for SM messages betweenthe UE 301 and the SMF 324, and act as a transparent pro9 for routing SMmessages. AMF 321 can also provide transport for SMS messages between UE301 and an SMSF (not shown by FIG. 3). AMF 321 can act as SEAF, whichcan include interaction with the AUSF 322 and the UE 301, receipt of anintermediate key that was established as a result of the UE 301authentication process. Where USIM based authentication is used, the AMF321 can retrieve the security material from the AUSF 322. AMF 321 canalso include a SCM function, which receives a key from the SEA that ituses to derive access-network specific keys. Furthermore, AMF 321 can bea termination point of a RAN CP interface, which can include or be an N2reference point between the (R)AN 310 and the AMF 321; and the AMF 321can be a termination point of NAS (N1) signaling, and perform NASciphering and integrity protection.

AMF 321 can also support NAS signaling with a UE 301 over an N3 IWFinterface. The N3IWF can be used to provide access to untrustedentities. N3IWF can be a termination point for the N2 interface betweenthe (R)AN 310 and the AMF 321 for the control plane, and can be atermination point for the N3 reference point between the (R)AN 310 andthe UPF 302 for the user plane. As such, the AMF 321 can handle N2signaling from the SMF 324 and the AMF 321 for PDU sessions and QoS,encapsulate/de-encapsulate packets for IPSec and N3 tunneling, mark N3user-plane packets in the uplink, and enforce QoS corresponding to N3packet marking taking into account QoS requirements associated with suchmarking received over N2. N3IWF can also relay uplink and downlinkcontrol-plane NAS signaling between the UE 301 and AMF 321 via an N1reference point between the UE 301 and the AMF 321, and relay uplink anddownlink user-plane packets between the UE 301 and UPF 302. The N3IWFalso provides mechanisms for IPsec tunnel establishment with the UE 301.The AMF 321 can exhibit an Namf service-based interface, and can be atermination point for an N14 reference point between two AMFs 321 and anN17 reference point between the AMF 321 and a 5G-EIR (not shown by FIG.3).

The UE 301 can need to register with the AMF 321 in order to receivenetwork services. RM is used to register or deregister the UE 301 withthe network (e.g., AMF 321), and establish a UE context in the network(e.g., AMF 321). The UE 301 can operate in an RM-REGISTERED state or anRM-DEREGISTERED state. In the RM DEREGISTERED state, the UE 301 is notregistered with the network, and the UE context in AMF 321 holds novalid location or routing information for the UE 301 so the UE 301 isnot reachable by the AMF 321. In the RM REGISTERED state, the UE 301 isregistered with the network, and the UE context in AMF 321 can hold avalid location or routing information for the UE 301 so the UE 301 isreachable by the AMF 321. In the RM-REGISTERED state, the UE 301 canperform mobility Registration Update procedures, perform periodicRegistration Update procedures triggered by expiration of the periodicupdate timer (e.g., to notify the network that the UE 301 is stillactive), and perform a Registration Update procedure to update UEcapability information or to re-negotiate protocol parameters with thenetwork, among others.

The AMF 321 can store one or more RM contexts for the UE 301, where eachRM context is associated with a specific access to the network. The RMcontext can be a data structure, database object, etc. That indicates orstores, inter alia, a registration state per access type and theperiodic update timer. The AMF 321 can also store a 5GC MM context thatcan be the same or similar to the (E)MM context discussed previously. Invarious implementations, the AMF 321 can store a CE mode B Restrictionparameter of the UE 301 in an associated MM context or RM context. TheAMF 321 can also derive the value, when needed, from the UE's usagesetting parameter already stored in the UE context (and/or MM/RMcontext).

CM can be used to establish and release a signaling connection betweenthe UE 301 and the AMF 321 over the N1 interface. The signalingconnection is used to enable NAS signaling exchange between the UE 301and the CN 320, and includes both the signaling connection between theUE and the AN (e.g., RRC connection or UE-N3IWF connection for non-3GPPaccess) and the N2 connection for the UE 301 between the AN (e.g., RAN310) and the AMF 321. The UE 301 can operate in one of two CM states,CM-IDLE mode or CM-CONNECTED mode. When the UE 301 is operating in theCM-IDLE state/mode, the UE 301 can have no NAS signaling connectionestablished with the AMF 321 over the N1 interface, and there can be(R)AN 310 signaling connection (e.g., N2 and/or N3 connections) for theUE 301. When the UE 301 is operating in the CM-CONNECTED state/mode, theUE 301 can have an established NAS signaling connection with the AMF 321over the N1 interface, and there can be a (R)AN 310 signaling connection(e.g., N2 and/or N3 connections) for the UE 301. Establishment of an N2connection between the (R)AN 310 and the AMF 321 can cause the UE 301 totransition from CM-IDLE mode to CM-CONNECTED mode, and the UE 301 cantransition from the CM-CONNECTED mode to the CM-IDLE mode when N2signaling between the (R)AN 310 and the AMF 321 is released.

The SMF 324 can be responsible for SM (e.g., session establishment,modify and release, including tunnel maintain between UPF and AN node);UE IP address allocation and management (including optionalauthorization); selection and control of UP function; configuringtraffic steering at UPF to route traffic to proper destination;termination of interfaces toward policy control functions; controllingpart of policy enforcement and QoS; lawful intercept (for SM events andinterface to LI system); termination of SM parts of NAS messages;downlink data notification; initiating AN specific SM information, sentvia AMF over N2 to AN; and determining SSC mode of a session. SM canrefer to management of a PDU session, and a PDU session or “session” canrefer to a PDU connectivity service that provides or enables theexchange of PDUs between a UE 301 and a data network (DN) 303 identifiedby a Data Network Name (DNN). PDU sessions can be established upon UE301 request, modified upon UE 301 and 5GC 320 request, and released uponUE 301 and 5GC 320 request using NAS SM signaling exchanged over the N1reference point between the UE 301 and the SMF 324. Upon request from anapplication server, the 5GC 320 can trigger a specific application inthe UE 301. In response to receipt of the trigger message, the UE 301can pass the trigger message (or relevant parts/information of thetrigger message) to one or more identified applications in the UE 301.The identified application(s) in the UE 301 can establish a PDU sessionto a specific DNN. The SMF 324 can check whether the UE 301 requests arecompliant with user subscription information associated with the UE 301.In this regard, the SMF 324 can retrieve and/or request to receiveupdate notifications on SMF 324 level subscription data from the UDM327.

The SMF 324 can include the following roaming functionality: handlinglocal enforcement to apply QoS SLAB (VPLMN); charging data collectionand charging interface (VPLMN); lawful intercept (in VPLMN for SM eventsand interface to LI system); and support for interaction with externalDN for transport of signaling for PDU sessionauthorization/authentication by external DN. An N16 reference pointbetween two SMFs 324 can be included in the system 300, which can bebetween another SMF 324 in a visited network and the SMF 324 in the homenetwork in roaming scenarios. Additionally, the SMF 324 can exhibit theNsmf service-based interface.

The NEF 323 can provide means for securely exposing the services andcapabilities provided by 3GPP network functions for third party,internal exposure/re-exposure, Application Functions (e.g., AF 328),edge computing or fog computing systems, etc. In such implementations,the NEF 323 can authenticate, authorize, and/or throttle the AFs. NEF323 can also translate information exchanged with the AF 328 andinformation exchanged with internal network functions. For example, theNEF 323 can translate between an AF-Service-Identifier and an internal5GC information. NEF 323 can also receive information from other networkfunctions (NFs) based on exposed capabilities of other networkfunctions. This information can be stored at the NEF 323 as structureddata, or at a data storage NF using standardized interfaces. The storedinformation can then be re-exposed by the NEF 323 to other NFs and AFs,and/or used for other purposes such as analytics. Additionally, the NEF323 can exhibit an Nnef service-based interface.

The NRF 325 can support service discovery functions, receive NFdiscovery requests from NF instances, and provide the information of thediscovered NF instances to the NF instances. NRF 325 also maintainsinformation of available NF instances and their supported services. Asused herein, the terms “instantiate,” “instantiation,” and the like canrefer to the creation of an instance, and an “instance” can refer to aconcrete occurrence of an object, which can occur, for example, duringexecution of program code. Additionally, the NRF 325 can exhibit theNnrf service-based interface.

The PCF 326 can provide policy rules to control plane function(s) toenforce them, and can also support unified policy framework to governnetwork behavior. The PCF 326 can also implement an FE to accesssubscription information relevant for policy decisions in a UDR of theUDM 327. The PCF 326 can communicate with the AMF 321 via an N15reference point between the PCF 326 and the AMF 321, which can include aPCF 326 in a visited network and the AMF 321 in case of roamingscenarios. The PCF 326 can communicate with the AF 328 via an N5reference point between the PCF 326 and the AF 328; and with the SMF 324via an N7 reference point between the PCF 326 and the SMF 324. Thesystem 300 and/or CN 320 can also include an N24 reference point betweenthe PCF 326 (in the home network) and a PCF 326 in a visited network.Additionally, the PCF 326 can exhibit an Npcf service-based interface.

The UDM 327 can handle subscription-related information to support thenetwork entities' handling of communication sessions, and can storesubscription data of UE 301. For example, subscription data can becommunicated between the UDM 327 and the AMF 321 via an N8 referencepoint between the UDM 327 and the AMF. The UDM 327 can include twoparts, an application FE and a UDR (the FE and UDR are not shown by FIG.3). The UDR can store subscription data and policy data for the UDM 327and the PCF 326, and/or structured data for exposure and applicationdata (including PFDs for application detection, application requestinformation for multiple UEs 301) for the NEF 323. The Nudrservice-based interface can be exhibited by the UDR 221 to allow the UDM327, PCF 326, and NEF 323 to access a particular set of the stored data,as well as to read, update (e.g., add, modify), delete, and subscribe tonotification of relevant data changes in the UDR. The UDM can include aUDM-FE, which is in charge of processing credentials, locationmanagement, subscription management, and so on. Several different frontends can serve the same user in different transactions. The UDM-FEaccesses subscription information stored in the UDR and performsauthentication credential processing, user identification handling,access authorization, registration/mobility management, and subscriptionmanagement. The UDR can interact with the SMF 324 via an N10 referencepoint between the UDM 327 and the SMF 324. UDM 327 can also support SMSmanagement, wherein an SMS-FE implements the similar application logicas discussed previously. Additionally, the UDM 327 can exhibit the Nudmservice-based interface.

The AF 328 can provide application influence on traffic routing, provideaccess to the NCE, and interact with the policy framework for policycontrol. The NCE can be a mechanism that allows the 5GC 320 and AF 328to provide information to each other via NEF 323, which can be used foredge computing implementations. In such implementations, the networkoperator and third party services can be hosted close to the UE 301access point of attachment to achieve an efficient service deliverythrough the reduced end-to-end latency and load on the transportnetwork. For edge computing implementations, the 5GC can select a UPF302 close to the UE 301 and execute traffic steering from the UPF 302 toDN 303 via the N6 interface. This can be based on the UE subscriptiondata, UE location, and information provided by the AF 328. In this way,the AF 328 can influence UPF (re)selection and traffic routing. Based onoperator deployment, when AF 328 is considered to be a trusted entity,the network operator can permit AF 328 to interact directly withrelevant NFs. Additionally, the AF 328 can exhibit an Naf service-basedinterface.

The NSSF 329 can select a set of network slice instances serving the UE301. The NSSF 329 can also determine allowed NSSAI and the mapping tothe subscribed S-NSSAIs, if needed. The NSSF 329 can also determine theAMF set to be used to serve the UE 301, or a list of candidate AMF(s)321 based on a suitable configuration and possibly by querying the NRF325. The selection of a set of network slice instances for the UE 301can be triggered by the AMF 321 with which the UE 301 is registered byinteracting with the NSSF 329, which can lead to a change of AMF 321.The NSSF 329 can interact with the AMF 321 via an N22 reference pointbetween AMF 321 and NSSF 329; and can communicate with another NSSF 329in a visited network via an N31 reference point (not shown by FIG. 3).Additionally, the NSSF 329 can exhibit an Nnssf service-based interface.

As discussed previously, the CN 320 can include an SMSF, which can beresponsible for SMS subscription checking and verification, and relayingSM messages to/from the UE 301 to/from other entities, such as anSMS-GMSC/IWMSC/SMS-router. The SMS can also interact with AMF 321 andUDM 327 for a notification procedure that the UE 301 is available forSMS transfer (e.g., set a UE not reachable flag, and notifying UDM 327when UE 301 is available for SMS).

The CN 120 can also include other elements that are not shown by FIG. 3,such as a Data Storage system/architecture, a 5G-EIR, a SEPP, and thelike. The Data Storage system can include a SDSF, an UDSF, and/or thelike. Any NF can store and retrieve unstructured data into/from the UDSF(e.g., UE contexts), via N18 reference point between any NF and the UDSF(not shown by FIG. 3). Individual NFs can share a UDSF for storing theirrespective unstructured data or individual NFs can each have their ownUDSF located at or near the individual NFs. Additionally, the UDSF canexhibit an Nudsf service-based interface (not shown by FIG. 3). The5G-EIR can be an NF that checks the status of PEI for determiningwhether particular equipment/entities are blacklisted from the network;and the SEPP can be a non-transparent pro9 that performs topologyhiding, message filtering, and policing on inter-PLMN control planeinterfaces.

Additionally, there can be many more reference points and/orservice-based interfaces between the NF services in the NFs; however,these interfaces and reference points have been omitted from FIG. 3 forclarity. In one example, the CN 320 can include an Nx interface, whichis an inter-CN interface between the MME (e.g., MME 221) and the AMF 321in order to enable interworking between CN 320 and CN 220. Other exampleinterfaces/reference points can include an N5g-EIR service-basedinterface exhibited by a 5G-EIR, an N27 reference point between the NRFin the visited network and the NRF in the home network; and an N31reference point between the NSSF in the visited network and the NSSF inthe home network.

FIG. 4 illustrates an example of infrastructure equipment 400 inaccordance with one or more implementations. The infrastructureequipment 400 (or “system 400”) can be implemented as a base station,radio head, RAN node such as the RAN nodes 111 and/or AP 106 shown anddescribed previously, application server(s) 130, and/or any otherelement/device discussed herein. In other examples, the system 400 couldbe implemented in or by a UE.

The system 400 includes application circuitry 405, baseband circuitry410, one or more radio front end modules (RFEMs) 415, memory circuitry420, power management integrated circuitry (PMIC) 425, power teecircuitry 430, network controller circuitry 435, network interfaceconnector 440, satellite positioning circuitry 445, and user interface450. In some implementations, the device 400 can include additionalelements such as, for example, memory/storage, display, camera, sensor,or input/output (I/O) interface. In other implementations, thecomponents described below can be included in more than one device. Forexample, said circuitries can be separately included in more than onedevice for CRAN, vBBU, or other like implementations.

Application circuitry 405 includes circuitry such as, but not limited toone or more processors (or processor cores), cache memory, and one ormore of low drop-out voltage regulators (LDOs), interrupt controllers,serial interfaces such as SPI, I2C or universal programmable serialinterface module, real time clock (RTC), timer-counters includinginterval and watchdog timers, general purpose input/output (I/O or IO),memory card controllers such as Secure Digital (SD) MultiMediaCard (MMC)or similar, Universal Serial Bus (USB) interfaces, Mobile IndustryProcessor Interface (MIPI) interfaces and Joint Test Access Group (JTAG)test access ports. The processors (or cores) of the applicationcircuitry 405 can be coupled with or can include memory/storage elementsand can be configured to execute instructions stored in thememory/storage to enable various applications or operating systems torun on the system 400. In some implementations, the memory/storageelements can be on-chip memory circuitry, which can include any suitablevolatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM,Flash memory, solid-state memory, and/or any other type of memory devicetechnology, such as those discussed herein.

The processor(s) of application circuitry 405 can include, for example,one or more processor cores (CPUs), one or more application processors,one or more graphics processing units (GPUs), one or more reducedinstruction set computing (RISC) processors, one or more Acorn RISCMachine (ARM) processors, one or more complex instruction set computing(CISC) processors, one or more digital signal processors (DSP), one ormore FPGAs, one or more PLDs, one or more ASICs, one or moremicroprocessors or controllers, or any suitable combination thereof. Insome implementations, the application circuitry 405 can include, or canbe, a special-purpose processor/controller to operate according to thevarious implementations herein. As examples, the processor(s) ofapplication circuitry 405 can include one or more Apple A-seriesprocessors, Intel Pentium®, Core®, or Xeon® processor(s); Advanced MicroDevices (AMD) Ryzen® processor(s), Accelerated Processing Units (APUs),or Epyc® processors; ARM-based processor(s) licensed from ARM Holdings,Ltd. Such as the ARM Cortex-A family of processors and the ThunderX2®provided by Cavium™, Inc.; a MIPS-based design from MIPS Technologies,Inc. Such as MIPS Warrior P-class processors; and/or the like. In someimplementations, the system 400 does not utilize application circuitry405, and instead can include a special-purpose processor/controller toprocess IP data received from an EPC or 5GC, for example.

In some implementations, the application circuitry 405 can include oneor more hardware accelerators, which can be microprocessors,programmable processing devices, or the like. The one or more hardwareaccelerators can include, for example, computer vision (CV) and/or deeplearning (DL) accelerators. As examples, the programmable processingdevices can be one or more a field-programmable devices (FPDs) such asfield-programmable gate arrays (FPGAs) and the like; programmable logicdevices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs(HCPLDs), and the like; ASICs such as structured ASICs and the like;programmable SoCs (PSoCs); and the like. In such implementations, thecircuitry of application circuitry 405 can include logic blocks or logicfabric, and other interconnected resources that can be programmed toperform various functions, such as the procedures, methods, functions,etc. Of the various implementations discussed herein. In suchimplementations, the circuitry of application circuitry 405 can includememory cells (e.g., erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), flashmemory, static memory (e.g., static random access memory (SRAM),anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc.In look-up-tables (LUTs) and the like.

The baseband circuitry 410 can be implemented, for example, as asolder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module containing two or more integrated circuits. Thevarious hardware electronic elements of baseband circuitry 410 arediscussed infra with regard to FIG. 6.

User interface circuitry 450 can include one or more user interfacesdesigned to enable user interaction with the system 400 or peripheralcomponent interfaces designed to enable peripheral component interactionwith the system 400. User interfaces can include, but are not limitedto, one or more physical or virtual buttons (e.g., a reset button), oneor more indicators (e.g., light emitting diodes (LEDs)), a physicalkeyboard or keypad, a mouse, a touchpad, a touchscreen, speakers orother audio emitting devices, microphones, a printer, a scanner, aheadset, a display screen or display device, etc. Peripheral componentinterfaces can include, but are not limited to, a nonvolatile memoryport, a universal serial bus (USB) port, an audio jack, a power supplyinterface, etc.

The radio front end modules (RFEMs) 415 can include a millimeter wave(mmWave) RFEM and one or more sub-mmWave radio frequency integratedcircuits (RFICs). In some implementations, the one or more sub-mmWaveRFICs can be physically separated from the mmWave RFEM. The RFICs caninclude connections to one or more antennas or antenna arrays (see e.g.,antenna array 611 of FIG. 6 infra), and the RFEM can be connected tomultiple antennas. In alternative implementations, both mmWave andsub-mmWave radio functions can be implemented in the same physical RFEM415, which incorporates both mmWave antennas and sub-mmWave.

The memory circuitry 420 can include one or more of volatile memoryincluding dynamic random access memory (DRAM) and/or synchronous dynamicrandom access memory (SDRAM), and nonvolatile memory (NVM) includinghigh-speed electrically erasable memory (commonly referred to as Flashmemory), phase change random access memory (PRAM), magnetoresistiverandom access memory (MRAM), etc., and can incorporate thethree-dimensional (3D) cross-point (XPOINT) memories from Intel® andMicron®. Memory circuitry 420 can be implemented as one or more ofsolder down packaged integrated circuits, socketed memory modules andplug-in memory cards.

The PMIC 425 can include voltage regulators, surge protectors, poweralarm detection circuitry, and one or more backup power sources such asa battery or capacitor. The power alarm detection circuitry can detectone or more of brown out (under-voltage) and surge (over-voltage)conditions. The power tee circuitry 430 can provide for electrical powerdrawn from a network cable to provide both power supply and dataconnectivity to the infrastructure equipment 400 using a single cable.

The network controller circuitry 435 can provide connectivity to anetwork using a standard network interface protocol such as Ethernet,Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching(MPLS), or some other suitable protocol. Network connectivity can beprovided to/from the infrastructure equipment 400 via network interfaceconnector 440 using a physical connection, which can be electrical(commonly referred to as a “copper interconnect”), optical, or wireless.The network controller circuitry 435 can include one or more dedicatedprocessors and/or FPGAs to communicate using one or more of theaforementioned protocols. In some implementations, the networkcontroller circuitry 435 can include multiple controllers to provideconnectivity to other networks using the same or different protocols.

The positioning circuitry 445 includes circuitry to receive and decodesignals transmitted/broadcasted by a positioning network of a globalnavigation satellite system (GNSS). Examples of navigation satelliteconstellations (or GNSS) include United States' Global PositioningSystem (GPS), Russia's Global Navigation System (GLONASS), the EuropeanUnion's Galileo system, China's BeiDou Navigation Satellite System, aregional navigation system or GNSS augmentation system (e.g., Navigationwith Indian Constellation (NAVIC), Japan's Quasi-Zenith Satellite System(QZSS), France's Doppler Orbitography and Radio-positioning Integratedby Satellite (DORIS), etc.), or the like. The positioning circuitry 445includes various hardware elements (e.g., including hardware devicessuch as switches, filters, amplifiers, antenna elements, and the like tofacilitate OTA communications) to communicate with components of apositioning network, such as navigation satellite constellation nodes.In some implementations, the positioning circuitry 445 can include aMicro-Technology for Positioning, Navigation, and Timing (Micro-PNT) ICthat uses a master timing clock to perform position tracking/estimationwithout GNSS assistance. The positioning circuitry 445 can also be partof, or interact with, the baseband circuitry 410 and/or RFEMs 415 tocommunicate with the nodes and components of the positioning network.The positioning circuitry 445 can also provide position data and/or timedata to the application circuitry 405, which can use the data tosynchronize operations with various infrastructure (e.g., RAN nodes 111,etc.), or the like.

The components shown by FIG. 4 can communicate with one another usinginterface circuitry, which can include any number of bus and/orinterconnect (IX) technologies such as industry standard architecture(ISA), extended ISA (EISA), peripheral component interconnect (PCI),peripheral component interconnect extended (PCIx), PCI express (PCIe),or any number of other technologies. The bus/IX can be a proprietarybus, for example, used in a SoC based system. Other bus/IX systems canbe included, such as an I2C interface, an SPI interface, point to pointinterfaces, and a power bus, among others.

FIG. 5 illustrates an example of a platform 500 (or “device 500”) inaccordance with one or more implementations. In implementations, thecomputer platform 500 can be suitable for use as UEs 101, 201, 301,application servers 130, and/or any other element/device discussedherein. The platform 500 can include any combinations of the componentsshown in the example. The components of platform 500 can be implementedas integrated circuits (ICs), portions thereof, discrete electronicdevices, or other modules, logic, hardware, software, firmware, or acombination thereof adapted in the computer platform 500, or ascomponents otherwise incorporated within a chassis of a larger system.The block diagram of FIG. 5 is intended to show a high level view ofcomponents of the computer platform 500. However, some of the componentsshown can be omitted, additional components can be present, anddifferent arrangement of the components shown can occur in otherimplementations.

Application circuitry 505 includes circuitry such as, but not limited toone or more processors (or processor cores), cache memory, and one ormore of LDOs, interrupt controllers, serial interfaces such as SPI, I2Cor universal programmable serial interface module, RTC, timer-countersincluding interval and watchdog timers, general purpose I/O, memory cardcontrollers such as SD MMC or similar, USB interfaces, MIPI interfaces,and JTAG test access ports. The processors (or cores) of the applicationcircuitry 505 can be coupled with or can include memory/storage elementsand can be configured to execute instructions stored in thememory/storage to enable various applications or operating systems torun on the system 500. In some implementations, the memory/storageelements can be on-chip memory circuitry, which can include any suitablevolatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM,Flash memory, solid-state memory, and/or any other type of memory devicetechnology, such as those discussed herein.

The processor(s) of application circuitry 405 can include, for example,one or more processor cores, one or more application processors, one ormore GPUs, one or more RISC processors, one or more ARM processors, oneor more CISC processors, one or more DSP, one or more FPGAs, one or morePLDs, one or more ASICs, one or more microprocessors or controllers, amultithreaded processor, an ultra-low voltage processor, an embeddedprocessor, some other known processing element, or any suitablecombination thereof. In some implementations, the application circuitry405 can include, or can be, a special-purpose processor/controller tooperate according to the various implementations herein.

As examples, the processor(s) of application circuitry 505 can includean Apple A-series processor. The processors of the application circuitry505 can also be one or more of an Intel® Architecture Core™ basedprocessor, such as a Quark™, an Atom™, an i3, an i5, an i7, or anMCU-class processor, or another such processor available from Intel®Corporation, Santa Clara, Calif.; Advanced Micro Devices (AMD) Ryzen®processor(s) or Accelerated Processing Units (APUs); Snapdragon™processor(s) from Qualcomm® Technologies, Inc., Texas Instruments, Inc.®Open Multimedia Applications Platform (OMAP)™ processor(s); a MIPS-baseddesign from MIPS Technologies, Inc. such as MIPS Warrior M-class,Warrior I-class, and Warrior P-class processors; an ARM-based designlicensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R,and Cortex-M family of processors; or the like. In some implementations,the application circuitry 505 can be a part of a system on a chip (SoC)in which the application circuitry 505 and other components are formedinto a single integrated circuit.

Additionally or alternatively, application circuitry 505 can includecircuitry such as, but not limited to, one or more a field-programmabledevices (FPDs) such as FPGAs and the like; programmable logic devices(PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), andthe like; ASICs such as structured ASICs and the like; programmable SoCs(PSoCs); and the like. In such implementations, the circuitry ofapplication circuitry 505 can include logic blocks or logic fabric, andother interconnected resources that can be programmed to perform variousfunctions, such as the procedures, methods, functions, etc. Of thevarious implementations discussed herein. In such implementations, thecircuitry of application circuitry 505 can include memory cells (e.g.,erasable programmable read-only memory (EPROM), electrically erasableprogrammable read-only memory (EEPROM), flash memory, static memory(e.g., static random access memory (SRAM), anti-fuses, etc.)) used tostore logic blocks, logic fabric, data, etc. In look-up tables (LUTs)and the like.

The baseband circuitry 510 can be implemented, for example, as asolder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module containing two or more integrated circuits. Thevarious hardware electronic elements of baseband circuitry 510 arediscussed infra with regard to FIG. 6.

The RFEMs 515 can include a millimeter wave (mmWave) RFEM and one ormore sub-mmWave radio frequency integrated circuits (RFICs). In someimplementations, the one or more sub-mmWave RFICs can be physicallyseparated from the mmWave RFEM. The RFICs can include connections to oneor more antennas or antenna arrays (see e.g., antenna array 611 of FIG.6 infra), and the RFEM can be connected to multiple antennas. Inalternative implementations, both mmWave and sub-mmWave radio functionscan be implemented in the same physical RFEM 515, which incorporatesboth mmWave antennas and sub-mmWave.

The memory circuitry 520 can include any number and type of memorydevices used to provide for a given amount of system memory. Asexamples, the memory circuitry 520 can include one or more of volatilememory including random access memory (RAM), dynamic RAM (DRAM) and/orsynchronous dynamic RAM (SDRAM), and nonvolatile memory (NVM) includinghigh-speed electrically erasable memory (commonly referred to as Flashmemory), phase change random access memory (PRAM), magnetoresistiverandom access memory (MRAM), etc. The memory circuitry 520 can bedeveloped in accordance with a Joint Electron Devices EngineeringCouncil (JEDEC) low power double data rate (LPDDR)-based design, such asLPDDR2, LPDDR3, LPDDR4, or the like. Memory circuitry 520 can beimplemented as one or more of solder down packaged integrated circuits,single die package (SDP), dual die package (DDP) or quad die package(Q17P), socketed memory modules, dual inline memory modules (DIMMs)including microDIMMs or MiniDIMMs, and/or soldered onto a motherboardvia a ball grid array (BGA). In low power implementations, the memorycircuitry 520 can be on-die memory or registers associated with theapplication circuitry 505. To provide for persistent storage ofinformation such as data, applications, operating systems and so forth,memory circuitry 520 can include one or more mass storage devices, whichcan include, inter alia, a solid state disk drive (SSDD), hard diskdrive (HDD), a micro HDD, resistance change memories, phase changememories, holographic memories, or chemical memories, among others. Forexample, the computer platform 500 can incorporate the three-dimensional(3D) cross-point (XPOINT) memories from Intel® and Micron®.

Removable memory circuitry 523 can include devices, circuitry,enclosures/housings, ports or receptacles, etc. Used to couple portabledata storage devices with the platform 500. These portable data storagedevices can be used for mass storage purposes, and can include, forexample, flash memory cards (e.g., Secure Digital (SD) cards, microSDcards, xD picture cards, and the like), and USB flash drives, opticaldiscs, external HDDs, and the like.

The platform 500 can also include interface circuitry (not shown) thatis used to connect external devices with the platform 500. The externaldevices connected to the platform 500 via the interface circuitryinclude sensor circuitry 521 and electro-mechanical components (EMCs)522, as well as removable memory devices coupled to removable memorycircuitry 523.

The sensor circuitry 521 include devices, modules, or subsystems whosepurpose is to detect events or changes in its environment and send theinformation (sensor data) about the detected events to some other adevice, module, subsystem, etc. Examples of such sensors include, interalia, inertia measurement units (IMUS) including accelerometers,gyroscopes, and/or magnetometers; microelectromechanical systems (MEMS)or nanoelectromechanical systems (NEMS) including 3-axis accelerometers,3-axis gyroscopes, and/or magnetometers; level sensors; flow sensors;temperature sensors (e.g., thermistors); pressure sensors; barometricpressure sensors; gravimeters; altimeters; image capture devices (e.g.,cameras or lensless apertures); light detection and ranging (LiDAR)sensors; proximity sensors (e.g., infrared radiation detector and thelike), depth sensors, ambient light sensors, ultrasonic transceivers;microphones or other like audio capture devices; etc.

EMCs 522 include devices, modules, or subsystems whose purpose is toenable platform 500 to change its state, position, and/or orientation,or move or control a mechanism or (sub)system. Additionally, EMCs 522can be configured to generate and send messages/signaling to othercomponents of the platform 500 to indicate a current state of the EMCs522. Examples of the EMCs 522 include one or more power switches, relaysincluding electromechanical relays (EMRs) and/or solid state relays(SSRs), actuators (e.g., valve actuators, etc.), an audible soundgenerator, a visual warning device, motors (e.g., DC motors, steppermotors, etc.), wheels, thrusters, propellers, claws, clamps, hooks,and/or other like electro-mechanical components. In implementations,platform 500 is configured to operate one or more EMCs 522 based on oneor more captured events and/or instructions or control signals receivedfrom a service provider and/or various clients.

In some implementations, the interface circuitry can connect theplatform 500 with positioning circuitry 545. The positioning circuitry545 includes circuitry to receive and decode signalstransmitted/broadcasted by a positioning network of a GNSS. Examples ofnavigation satellite constellations (or GNSS) include United States'GPS, Russia's GLONASS, the European Union's Galileo system, China'sBeiDou Navigation Satellite System, a regional navigation system or GNSSaugmentation system (e.g., NAVIC), Japan's QZSS, France's DORIS, etc.),or the like. The positioning circuitry 545 includes various hardwareelements (e.g., including hardware devices such as switches, filters,amplifiers, antenna elements, and the like to facilitate OTAcommunications) to communicate with components of a positioning network,such as navigation satellite constellation nodes. In someimplementations, the positioning circuitry 545 can include a Micro-PNTIC that uses a master timing clock to perform positiontracking/estimation without GNSS assistance. The positioning circuitry545 can also be part of, or interact with, the baseband circuitry 410and/or RFEMs 515 to communicate with the nodes and components of thepositioning network. The positioning circuitry 545 can also provideposition data and/or time data to the application circuitry 505, whichcan use the data to synchronize operations with various infrastructure(e.g., radio base stations), for turn-by-turn navigation applications,or the like.

In some implementations, the interface circuitry can connect theplatform 500 with Near-Field Communication (NFC) circuitry 540. NFCcircuitry 540 is configured to provide contactless, short-rangecommunications based on radio frequency identification (RFID) standards,wherein magnetic field induction is used to enable communication betweenNFC circuitry 540 and NFC-enabled devices external to the platform 500(e.g., an “NFC touchpoint”). NFC circuitry 540 includes an NFCcontroller coupled with an antenna element and a processor coupled withthe NFC controller. The NFC controller can be a chip/IC providing NFCfunctionalities to the NFC circuitry 540 by executing NFC controllerfirmware and an NFC stack. The NFC stack can be executed by theprocessor to control the NFC controller, and the NFC controller firmwarecan be executed by the NFC controller to control the antenna element toemit short-range RF signals. The RF signals can power a passive NFC tag(e.g., a microchip embedded in a sticker or wristband) to transmitstored data to the NFC circuitry 540, or initiate data transfer betweenthe NFC circuitry 540 and another active NFC device (e.g., a smartphoneor an NFC-enabled POS terminal) that is proximate to the platform 500.

The driver circuitry 546 can include software and hardware elements thatoperate to control particular devices that are embedded in the platform500, attached to the platform 500, or otherwise communicatively coupledwith the platform 500. The driver circuitry 546 can include individualdrivers allowing other components of the platform 500 to interact withor control various input/output (I/O) devices that can be presentwithin, or connected to, the platform 500. For example, driver circuitry546 can include a display driver to control and allow access to adisplay device, a touchscreen driver to control and allow access to atouchscreen interface of the platform 500, sensor drivers to obtainsensor readings of sensor circuitry 521 and control and allow access tosensor circuitry 521, EMC drivers to obtain actuator positions of theEMCs 522 and/or control and allow access to the EMCs 522, a cameradriver to control and allow access to an embedded image capture device,audio drivers to control and allow access to one or more audio devices.

The power management integrated circuitry (PMIC) 525 (also referred toas “power management circuitry 525”) can manage power provided tovarious components of the platform 500. In particular, with respect tothe baseband circuitry 510, the PMIC 525 can control power-sourceselection, voltage scaling, battery charging, or DC-to-DC conversion.The PMIC 525 can often be included when the platform 500 is capable ofbeing powered by a battery 530, for example, when the device is includedin a UE 101, 201, 301.

In some implementations, the PMIC 525 can control, or otherwise be partof, various power saving mechanisms of the platform 500. For example, ifthe platform 500 is in an RRC_Connected state, where it is stillconnected to the RAN node as it expects to receive traffic shortly, thenit can enter a state known as Discontinuous Reception Mode (DRX) after aperiod of inactivity. During this state, the platform 500 can power downfor brief intervals of time and thus save power. If there is no datatraffic activity for an extended period of time, then the platform 500can transition off to an RRC_Idle state, where it disconnects from thenetwork and does not perform operations such as channel qualityfeedback, handover, etc. The platform 500 goes into a very low powerstate and it performs paging where again it periodically wakes up tolisten to the network and then powers down again. The platform 500 doesnot receive data in this state; in order to receive data, it musttransition back to RRC_Connected state. An additional power saving modecan allow a device to be unavailable to the network for periods longerthan a paging interval (ranging from seconds to a few hours). Duringthis time, the device is totally unreachable to the network and canpower down completely. Any data sent during this time incurs a largedelay and it is assumed the delay is acceptable.

A battery 530 can power the platform 500, although in some examples theplatform 500 can be mounted deployed in a fixed location, and can have apower supply coupled to an electrical grid. The battery 530 can be alithium ion battery, a metal-air battery, such as a zinc-air battery, analuminum-air battery, a lithium-air battery, and the like. In someimplementations, such as in V2X applications, the battery 530 can be atypical lead-acid automotive battery.

In some implementations, the battery 530 can be a “smart battery,” whichincludes or is coupled with a Battery Management System (BMS) or batterymonitoring integrated circuitry. The BMS can be included in the platform500 to track the state of charge (SoCh) of the battery 530. The BMS canbe used to monitor other parameters of the battery 530 to providefailure predictions, such as the state of health (SoH) and the state offunction (SoF) of the battery 530. The BMS can communicate theinformation of the battery 530 to the application circuitry 505 or othercomponents of the platform 500. The BMS can also include ananalog-to-digital (ADC) convertor that allows the application circuitry505 to directly monitor the voltage of the battery 530 or the currentflow from the battery 530. The battery parameters can be used todetermine actions that the platform 500 can perform, such astransmission frequency, network operation, detecting frequency, and thelike.

A power block, or other power supply coupled to an electrical grid canbe coupled with the BMS to charge the battery 530. In some examples, thepower block XS30 can be replaced with a wireless power receiver toobtain the power wirelessly, for example, through a loop antenna in thecomputer platform 500. In these examples, a wireless battery chargingcircuit can be included in the BMS. The specific charging circuitschosen can depend on the size of the battery 530, and thus, the currentrequired. The charging can be performed using the Airfuel standardpromulgated by the Airfuel Alliance, the Qi wireless charging standardpromulgated by the Wireless Power Consortium, or the Rezence chargingstandard promulgated by the Alliance for Wireless Power, among others.

User interface circuitry 550 includes various input/output (I/O) devicespresent within, or connected to, the platform 500, and includes one ormore user interfaces designed to enable user interaction with theplatform 500 and/or peripheral component interfaces designed to enableperipheral component interaction with the platform 500. The userinterface circuitry 550 includes input device circuitry and outputdevice circuitry. Input device circuitry includes any physical orvirtual means for accepting an input including, inter alia, one or morephysical or virtual buttons (e.g., a reset button), a physical keyboard,keypad, mouse, touchpad, touchscreen, microphones, scanner, headset,and/or the like. The output device circuitry includes any physical orvirtual means for showing information or otherwise conveyinginformation, such as sensor readings, actuator position(s), or otherlike information. Output device circuitry can include any number and/orcombinations of audio or visual display, including, inter alia, one ormore simple visual outputs/indicators (e.g., binary status indicators(e.g., light emitting diodes (LEDs)) and multi-character visual outputs,or more complex outputs such as display devices or touchscreens (e.g.,Liquid Crystal Displays (LCD), LED displays, quantum dot displays,projectors, etc.), with the output of characters, graphics, multimediaobjects, and the like being generated or produced from the operation ofthe platform 500. The output device circuitry can also include speakersor other audio emitting devices, printer(s), and/or the like. In someimplementations, the sensor circuitry 521 can be used as the inputdevice circuitry (e.g., an image capture device, motion capture device,or the like) and one or more EMCs can be used as the output devicecircuitry (e.g., an actuator to provide haptic feedback or the like). Inanother example, NFC circuitry including an NFC controller coupled withan antenna element and a processing device can be included to readelectronic tags and/or connect with another NFC-enabled device.Peripheral component interfaces can include, but are not limited to, anon-volatile memory port, a USB port, an audio jack, a power supplyinterface, etc.

Although not shown, the components of platform 500 can communicate withone another using a suitable bus or interconnect (IX) technology, whichcan include any number of technologies, including ISA, EISA, PCI, PCIx,PCIe, a Time-Trigger Protocol (TTP) system, a FlexRay system, or anynumber of other technologies. The bus/IX can be a proprietary bus/IX,for example, used in a SoC based system. Other bus/IX systems can beincluded, such as an I2C interface, an SPI interface, point-to-pointinterfaces, and a power bus, among others.

FIG. 6 illustrates example components of baseband circuitry 610 andradio front end modules (RFEM) 615 in accordance with one or moreimplementations. The baseband circuitry 610 corresponds to the basebandcircuitry 410 and 510 of FIGS. 4 and 5, respectively. The RFEM 615corresponds to the RFEM 415 and 515 of FIGS. 4 and 5, respectively. Asshown, the RFEMs 615 can include Radio Frequency (RF) circuitry 606,front-end module (FEM) circuitry 608, antenna array 611 coupled togetherat least as shown.

The baseband circuitry 610 includes circuitry and/or control logicconfigured to carry out various radio/network protocol and radio controlfunctions that enable communication with one or more radio networks viathe RF circuitry 606. The radio control functions can include, but arenot limited to, signal modulation/demodulation, encoding/decoding, radiofrequency shifting, etc. In some implementations,modulation/demodulation circuitry of the baseband circuitry 610 caninclude Fast-Fourier Transform (FFT), precoding, or constellationmapping/demapping functionality. In some implementations,encoding/decoding circuitry of the baseband circuitry 610 can includeconvolution, tail-biting convolution, turbo, Viterbi, or Low DensityParity Check (LDPC) encoder/decoder functionality. Implementations ofmodulation/demodulation and encoder/decoder functionality are notlimited to these examples and can include other suitable functionalityin other implementations. The baseband circuitry 610 is configured toprocess baseband signals received from a receive signal path of the RFcircuitry 606 and to generate baseband signals for a transmit signalpath of the RF circuitry 606. The baseband circuitry 610 is configuredto interface with application circuitry 405/505 (see FIGS. 4 and 5) forgeneration and processing of the baseband signals and for controllingoperations of the RF circuitry 606. The baseband circuitry 610 canhandle various radio control functions.

The aforementioned circuitry and/or control logic of the basebandcircuitry 610 can include one or more single or multi-core processors.For example, the one or more processors can include a 3G basebandprocessor 604A, a 4G/LTE baseband processor 604B, a 5G/NR basebandprocessor 604C, or some other baseband processor(s) 604D for otherexisting generations, generations in development or to be developed inthe future (e.g., sixth generation (6G), etc.). In otherimplementations, some or all of the functionality of baseband processors604A-D can be included in modules stored in the memory 604G and executedvia a Central Processing Unit (CPU) 604E. In other implementations, someor all of the functionality of baseband processors 604A-D can beprovided as hardware accelerators (e.g., FPGAs, ASICs, etc.) loaded withthe appropriate bit streams or logic blocks stored in respective memorycells. In various implementations, the memory 604G can store programcode of a real-time OS (RTOS), which when executed by the CPU 604E (orother baseband processor), is to cause the CPU 604E (or other basebandprocessor) to manage resources of the baseband circuitry 610, scheduletasks, etc. Examples of the RTOS can include Operating System Embedded(OSE)™ provided by Enea®, Nucleus RTOS™ provided by Mentor Graphics®,Versatile Real-Time Executive (VRTX) provided by Mentor Graphics®,ThreadX™ provided by Express Logic®, FreeRTOS, REX OS provided byQualcomm®, OKL4 provided by Open Kernel (OK) Labs®, or any othersuitable RTOS, such as those discussed herein. In addition, the basebandcircuitry 610 includes one or more audio digital signal processor(s)(DSP) 604F. The audio DSP(s) 604F include elements forcompression/decompression and echo cancellation and can include othersuitable processing elements in other implementations.

In some implementations, each of the processors 604A-604E includerespective memory interfaces to send/receive data to/from the memory604G. The baseband circuitry 610 can further include one or moreinterfaces to communicatively couple to other circuitries/devices, suchas an interface to send/receive data to/from memory external to thebaseband circuitry 610; an application circuitry interface tosend/receive data to/from the application circuitry 405/505 of FIG.4-XT); an RF circuitry interface to send/receive data to/from RFcircuitry 606 of FIG. 6; a wireless hardware connectivity interface tosend/receive data to/from one or more wireless hardware elements (e.g.,Near Field Communication (NFC) components, Bluetooth®/Bluetooth® LowEnergy components, Wi-Fi® components, and/or the like); and a powermanagement interface to send/receive power or control signals to/fromthe PMIC 525.

In alternate implementations (which can be combined with the abovedescribed implementations), baseband circuitry 610 includes one or moredigital baseband systems, which are coupled with one another via aninterconnect subsystem and to a CPU subsystem, an audio subsystem, andan interface subsystem. The digital baseband subsystems can also becoupled to a digital baseband interface and a mixed-signal basebandsubsystem via another interconnect subsystem. Each of the interconnectsubsystems can include a bus system, point-to-point connections,network-on-chip (NOC) structures, and/or some other suitable bus orinterconnect technology, such as those discussed herein. The audiosubsystem can include DSP circuitry, buffer memory, program memory,speech processing accelerator circuitry, data converter circuitry suchas analog-to-digital and digital-to-analog converter circuitry, analogcircuitry including one or more of amplifiers and filters, and/or otherlike components. In an aspect of the present disclosure, basebandcircuitry 610 can include protocol processing circuitry with one or moreinstances of control circuitry (not shown) to provide control functionsfor the digital baseband circuitry and/or radio frequency circuitry(e.g., the radio front end modules 615).

Although not shown by FIG. 6, in some implementations, the basebandcircuitry 610 includes individual processing device(s) to operate one ormore wireless communication protocols (e.g., a “multi-protocol basebandprocessor” or “protocol processing circuitry”) and individual processingdevice(s) to implement PHY layer functions. In these implementations,the PHY layer functions include the aforementioned radio controlfunctions. In these implementations, the protocol processing circuitryoperates or implements various protocol layers/entities of one or morewireless communication protocols. In a first example, the protocolprocessing circuitry can operate LTE protocol entities and/or 5G/NRprotocol entities when the baseband circuitry 610 and/or RF circuitry606 are part of mmWave communication circuitry or some other suitablecellular communication circuitry. In the first example, the protocolprocessing circuitry would operate MAC, RLC, PDCP, SDAP, RRC, and NASfunctions. In a second example, the protocol processing circuitry canoperate one or more IEEE-based protocols when the baseband circuitry 610and/or RF circuitry 606 are part of a Wi-Fi communication system. In thesecond example, the protocol processing circuitry would operate Wi-FiMAC and logical link control (LLC) functions. The protocol processingcircuitry can include one or more memory structures (e.g., 604G) tostore program code and data for operating the protocol functions, aswell as one or more processing cores to execute the program code andperform various operations using the data. The baseband circuitry 610can also support radio communications for more than one wirelessprotocol.

The various hardware elements of the baseband circuitry 610 discussedherein can be implemented, for example, as a solder-down substrateincluding one or more integrated circuits (ICs), a single packaged ICsoldered to a main circuit board or a multi-chip module containing twoor more ICs. In one example, the components of the baseband circuitry610 can be suitably combined in a single chip or chipset, or disposed ona same circuit board. In another example, some or all of the constituentcomponents of the baseband circuitry 610 and RF circuitry 606 can beimplemented together such as, for example, a system on a chip (SoC) orSystem-in-Package (SiP). In another example, some or all of theconstituent components of the baseband circuitry 610 can be implementedas a separate SoC that is communicatively coupled with and RF circuitry606 (or multiple instances of RF circuitry 606). In yet another example,some or all of the constituent components of the baseband circuitry 610and the application circuitry 405/505 can be implemented together asindividual SoCs mounted to a same circuit board (e.g., a “multi-chippackage”).

In some implementations, the baseband circuitry 610 can provide forcommunication compatible with one or more radio technologies. Forexample, in some implementations, the baseband circuitry 610 can supportcommunication with an E-UTRAN or other WMAN, a WLAN, a WPAN.Implementations in which the baseband circuitry 610 is configured tosupport radio communications of more than one wireless protocol can bereferred to as multi-mode baseband circuitry.

RF circuitry 606 can enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious implementations, the RF circuitry 606 can include switches,filters, amplifiers, etc. To facilitate the communication with thewireless network. RF circuitry 606 can include a receive signal path,which can include circuitry to down-convert RF signals received from theFEM circuitry 608 and provide baseband signals to the baseband circuitry610. RF circuitry 606 can also include a transmit signal path, which caninclude circuitry to up-convert baseband signals provided by thebaseband circuitry 610 and provide RF output signals to the FEMcircuitry 608 for transmission.

In some implementations, the receive signal path of the RF circuitry 606can include mixer circuitry 606 a, amplifier circuitry 606 b and filtercircuitry 606 c. In some implementations, the transmit signal path ofthe RF circuitry 606 can include filter circuitry 606 c and mixercircuitry 606 a. RF circuitry 606 can also include synthesizer circuitry606 d for synthesizing a frequency for use by the mixer circuitry 606 aof the receive signal path and the transmit signal path. In someimplementations, the mixer circuitry 606 a of the receive signal pathcan be configured to down-convert RF signals received from the FEMcircuitry 608 based on the synthesized frequency provided by synthesizercircuitry 606 d. The amplifier circuitry 606 b can be configured toamplify the down-converted signals and the filter circuitry 606 c can bea low-pass filter (LPF) or band-pass filter (BPF) configured to removeunwanted signals from the down-converted signals to generate outputbaseband signals. Output baseband signals can be provided to thebaseband circuitry 610 for further processing. In some implementations,the output baseband signals can be zero-frequency baseband signals,although this is not a requirement. In some implementations, mixercircuitry 606 a of the receive signal path can include passive mixers,although the scope of the implementations is not limited in thisrespect.

In some implementations, the mixer circuitry 606 a of the transmitsignal path can be configured to up-convert input baseband signals basedon the synthesized frequency provided by the synthesizer circuitry 606 dto generate RF output signals for the FEM circuitry 608. The basebandsignals can be provided by the baseband circuitry 610 and can befiltered by filter circuitry 606 c.

In some implementations, the mixer circuitry 606 a of the receive signalpath and the mixer circuitry 606 a of the transmit signal path caninclude two or more mixers and can be arranged for quadraturedownconversion and upconversion, respectively. In some implementations,the mixer circuitry 606 a of the receive signal path and the mixercircuitry 606 a of the transmit signal path can include two or moremixers and can be arranged for image rejection (e.g., Hartley imagerejection). In some implementations, the mixer circuitry 606 a of thereceive signal path and the mixer circuitry 606 a of the transmit signalpath can be arranged for direct downconversion and direct upconversion,respectively. In some implementations, the mixer circuitry 606 a of thereceive signal path and the mixer circuitry 606 a of the transmit signalpath can be configured for super-heterodyne operation.

In some implementations, the output baseband signals and the inputbaseband signals can be analog baseband signals, although the scope ofthe implementations is not limited in this respect. In some alternateimplementations, the output baseband signals and the input basebandsignals can be digital baseband signals. In these alternateimplementations, the RF circuitry 606 can include analog-to-digitalconverter (ADC) and digital-to-analog converter (DAC) circuitry and thebaseband circuitry 610 can include a digital baseband interface tocommunicate with the RF circuitry 606.

In some dual-mode implementations, a separate radio IC circuitry can beprovided for processing signals for each spectrum, although the scope ofthe implementations is not limited in this respect.

In some implementations, the synthesizer circuitry 606 d can be afractional-N synthesizer or a fractional N/N+1 synthesizer, although thescope of the implementations is not limited in this respect as othertypes of frequency synthesizers can be suitable. For example,synthesizer circuitry 606 d can be a delta-sigma synthesizer, afrequency multiplier, or a synthesizer including a phase-locked loopwith a frequency divider.

The synthesizer circuitry 606 d can be configured to synthesize anoutput frequency for use by the mixer circuitry 606 a of the RFcircuitry 606 based on a frequency input and a divider control input. Insome implementations, the synthesizer circuitry 606 d can be afractional N/N+1 synthesizer.

In some implementations, frequency input can be provided by a voltagecontrolled oscillator (VCO), although that is not a requirement. Dividercontrol input can be provided by either the baseband circuitry 610 orthe application circuitry 405/505 depending on the desired outputfrequency. In some implementations, a divider control input (e.g., N)can be determined from a look-up table based on a channel indicated bythe application circuitry 405/505.

Synthesizer circuitry 606 d of the RF circuitry 606 can include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In some implementations, the divider can be a dual modulusdivider (DMD) and the phase accumulator can be a digital phaseaccumulator (DPA). In some implementations, the DMD can be configured todivide the input signal by either N or N+1 (e.g., based on a carry out)to provide a fractional division ratio. In some example implementations,the DLL can include a set of cascaded, tunable, delay elements, a phasedetector, a charge pump and a D-type flip-flop. In theseimplementations, the delay elements can be configured to break a VCOperiod up into Nd equal packets of phase, where Nd is the number ofdelay elements in the delay line. In this way, the DLL provides negativefeedback to help ensure that the total delay through the delay line isone VCO cycle.

In some implementations, synthesizer circuitry 606 d can be configuredto generate a carrier frequency as the output frequency, while in otherimplementations, the output frequency can be a multiple of the carrierfrequency (e.g., twice the carrier frequency, four times the carrierfrequency) and used in conjunction with quadrature generator and dividercircuitry to generate multiple signals at the carrier frequency withmultiple different phases with respect to each other. In someimplementations, the output frequency can be a LO frequency (fLO). Insome implementations, the RF circuitry 606 can include an IQ/polarconverter.

FEM circuitry 608 can include a receive signal path, which can includecircuitry configured to operate on RF signals received from antennaarray 611, amplify the received signals and provide the amplifiedversions of the received signals to the RF circuitry 606 for furtherprocessing. FEM circuitry 608 can also include a transmit signal path,which can include circuitry configured to amplify signals fortransmission provided by the RF circuitry 606 for transmission by one ormore of antenna elements of antenna array 611. In variousimplementations, the amplification through the transmit or receivesignal paths can be done solely in the RF circuitry 606, solely in theFEM circuitry 608, or in both the RF circuitry 606 and the FEM circuitry608.

In some implementations, the FEM circuitry 608 can include a TX/RXswitch to switch between transmit mode and receive mode operation. TheFEM circuitry 608 can include a receive signal path and a transmitsignal path. The receive signal path of the FEM circuitry 608 caninclude an LNA to amplify received RF signals and provide the amplifiedreceived RF signals as an output (e.g., to the RF circuitry 606). Thetransmit signal path of the FEM circuitry 608 can include a poweramplifier (PA) to amplify input RF signals (e.g., provided by RFcircuitry 606), and one or more filters to generate RF signals forsubsequent transmission by one or more antenna elements of the antennaarray 611.

The antenna array 611 includes one or more antenna elements, each ofwhich is configured convert electrical signals into radio waves totravel through the air and to convert received radio waves intoelectrical signals. For example, digital baseband signals provided bythe baseband circuitry 610 is converted into analog RF signals (e.g.,modulated waveform) that will be amplified and transmitted via theantenna elements of the antenna array 611 including one or more antennaelements (not shown). The antenna elements can be omnidirectional,direction, or a combination thereof. The antenna elements can be formedin a multitude of arranges as are known and/or discussed herein. Theantenna array 611 can include microstrip antennas or printed antennasthat are fabricated on the surface of one or more printed circuitboards. The antenna array 611 can be formed in as a patch of metal foil(e.g., a patch antenna) in a variety of shapes, and can be coupled withthe RF circuitry 606 and/or FEM circuitry 608 using metal transmissionlines or the like.

Processors of the application circuitry 405/505 and processors of thebaseband circuitry 610 can be used to execute elements of one or moreinstances of a protocol stack. For example, processors of the basebandcircuitry 610, alone or in combination, can be used execute Layer 3,Layer 2, or Layer 1 functionality, while processors of the applicationcircuitry 405/505 can utilize data (e.g., packet data) received fromthese layers and further execute Layer 4 functionality (e.g., TCP andUDP layers). As referred to herein, Layer 3 can include a RRC layer,described in further detail below. As referred to herein, Layer 2 caninclude a MAC layer, an RLC layer, and a PDCP layer, described infurther detail below. As referred to herein, Layer 1 can include a PHYlayer of a UE/RAN node, described in further detail below.

FIG. 7 illustrates various protocol functions that can be implemented ina wireless communication device according to one or moreimplementations. In particular, FIG. 7 includes an arrangement 700showing interconnections between various protocol layers/entities. Thefollowing description of FIG. 7 is provided for various protocollayers/entities that operate in conjunction with the 5G/NR systemstandards and LTE system standards, but some or all of the aspects ofFIG. 7 can be applicable to other wireless communication network systemsas well.

The protocol layers of arrangement 700 can include one or more of PHY710, MAC 720, RLC 730, PDCP 740, SDAP 747, RRC 755, and NAS layer 757,in addition to other higher layer functions not illustrated. Theprotocol layers can include one or more service access points (e.g.,items 759, 756, 750, 749, 745, 735, 725, and 715 in FIG. 7) that canprovide communication between two or more protocol layers.

The PHY 710 can transmit and receive physical layer signals 705 that canbe received from or transmitted to one or more other communicationdevices. The physical layer signals 705 can include one or more physicalchannels, such as those discussed herein. The PHY 710 can furtherperform link adaptation or adaptive modulation and coding (AMC), powercontrol, cell search (e.g., for initial synchronization and handoverpurposes), and other measurements used by higher layers, such as the RRC755. The PHY 710 can still further perform error detection on thetransport channels, forward error correction (FEC) coding/decoding ofthe transport channels, modulation/demodulation of physical channels,interleaving, rate matching, mapping onto physical channels, and MIMOantenna processing. In implementations, an instance of PHY 710 canprocess requests from and provide indications to an instance of MAC 720via one or more PHY-SAP 715. According to some implementations, requestsand indications communicated via PHY-SAP 715 can include one or moretransport channels.

Instance(s) of MAC 720 can process requests from, and provideindications to, an instance of RLC 730 via one or more MAC-SAPs 725.These requests and indications communicated via the MAC-SAP 725 caninclude one or more logical channels. The MAC 720 can perform mappingbetween the logical channels and transport channels, multiplexing of MACSDUs from one or more logical channels onto TBs to be delivered to PHY710 via the transport channels, de-multiplexing MAC SDUs to one or morelogical channels from TBs delivered from the PHY 710 via transportchannels, multiplexing MAC SDUs onto TBs, scheduling informationreporting, error correction through HARQ, and logical channelprioritization.

Instance(s) of RLC 730 can process requests from and provide indicationsto an instance of PDCP 740 via one or more radio link control serviceaccess points (RLC-SAP) 735. These requests and indications communicatedvia RLC-SAP 735 can include one or more RLC channels. The RLC 730 canoperate in multiple modes of operation, including: Transparent Mode™,Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC 730 canexecute transfer of upper layer protocol data units (PDUs), errorcorrection through automatic repeat request (ARQ) for AM data transfers,and concatenation, segmentation and reassembly of RLC SDUs for UM and AMdata transfers. The RLC 730 can also execute re-segmentation of RLC dataPDUs for AM data transfers, reorder RLC data PDUs for UM and AM datatransfers, detect duplicate data for UM and AM data transfers, discardRLC SDUs for UM and AM data transfers, detect protocol errors for AMdata transfers, and perform RLC re-establishment.

Instance(s) of PDCP 740 can process requests from and provideindications to instance(s) of RRC 755 and/or instance(s) of SDAP 747 viaone or more packet data convergence protocol service access points(PDCP-SAP) 745. These requests and indications communicated via PDCP-SAP745 can include one or more radio bearers. The PDCP 740 can executeheader compression and decompression of IP data, maintain PDCP SequenceNumbers (SNs), perform in-sequence delivery of upper layer PDUs atre-establishment of lower layers, eliminate duplicates of lower layerSDUs at re-establishment of lower layers for radio bearers mapped on RLCAM, cipher and decipher control plane data, perform integrity protectionand integrity verification of control plane data, control timer-baseddiscard of data, and perform security operations (e.g., ciphering,deciphering, integrity protection, integrity verification, etc.).

Instance(s) of SDAP 747 can process requests from and provideindications to one or more higher layer protocol entities via one ormore SDAP-SAP 749. These requests and indications communicated viaSDAP-SAP 749 can include one or more QoS flows. The SDAP 747 can map QoSflows to DRBs, and vice versa, and can also mark QFIs in DL and ULpackets. A single SDAP entity 747 can be configured for an individualPDU session. In the UL direction, the NG-RAN 110 can control the mappingof QoS Flows to DRB(s) in two different ways, reflective mapping orexplicit mapping. For reflective mapping, the SDAP 747 of a UE 101 canmonitor the QFIs of the DL packets for each DRB, and can apply the samemapping for packets flowing in the UL direction. For a DRB, the SDAP 747of the UE 101 can map the UL packets belonging to the QoS flows(s)corresponding to the QoS flow ID(s) and PDU session observed in the DLpackets for that DRB. To enable reflective mapping, the NG-RAN 310 canmark DL packets over the Uu interface with a QoS flow ID. The explicitmapping can involve the RRC 755 configuring the SDAP 747 with anexplicit QoS flow to DRB mapping rule, which can be stored and followedby the SDAP 747. In implementations, the SDAP 747 can only be used in NRimplementations and is not used in LTE implementations.

The RRC 755 can configure, via one or more management service accesspoints (M-SAP), aspects of one or more protocol layers, which caninclude one or more instances of PHY 710, MAC 720, RLC 730, PDCP 740 andSDAP 747. In implementations, an instance of RRC 755 can processrequests from and provide indications to one or more NAS entities 757via one or more RRC-SAPs 756. The main services and functions of the RRC755 can include broadcast of system information (e.g., included in MIBsor SIBs related to the NAS), broadcast of system information related tothe access stratum (AS), paging, establishment, maintenance and releaseof an RRC connection between the UE 101 and RAN 110 (e.g., RRCconnection paging, RRC connection establishment, RRC connectionmodification, and RRC connection release), establishment, configuration,maintenance and release of point to point Radio Bearers, securityfunctions including key management, inter-RAT mobility, and measurementconfiguration for UE measurement reporting. The MIBs and SIBs caninclude one or more IEs, which can each include individual data fieldsor data structures.

The NAS 757 can form the highest stratum of the control plane betweenthe UE 101 and the AMF 321. The NAS 757 can support the mobility of theUEs 101 and the session management procedures to establish and maintainIP connectivity between the UE 101 and a P-GW in LTE systems.

According to various implementations, one or more protocol entities ofarrangement 700 can be implemented in UEs 101, RAN nodes 111, AMF 321 inNR implementations or MME 221 in LTE implementations, UPF 302 in NRimplementations or S-GW 222 and P-GW 223 in LTE implementations, or thelike to be used for control plane or user plane communications protocolstack between the aforementioned devices. In such implementations, oneor more protocol entities that can be implemented in one or more of UE101, gNB 111, AMF 321, etc. Can communicate with a respective peerprotocol entity that can be implemented in or on another device usingthe services of respective lower layer protocol entities to perform suchcommunication. In some implementations, a gNB-CU of the gNB 111 can hostthe RRC 755, SDAP 747, and PDCP 740 of the gNB that controls theoperation of one or more gNB-DUs, and the gNB-DUs of the gNB 111 caneach host the RLC 730, MAC 720, and PHY 710 of the gNB 111.

In a first example, a control plane protocol stack can include, in orderfrom highest layer to lowest layer, NAS 757, RRC 755, PDCP 740, RLC 730,MAC 720, and PHY 710. In this example, upper layers 760 can be built ontop of the NAS 757, which includes an IP layer 761, an SCTP 762, and anapplication layer signaling protocol (AP) 763.

In NR implementations, the AP 763 can be an NG application protocollayer (NGAP or NG-AP) 763 for the NG interface 113 defined between theNG-RAN node 111 and the AMF 321, or the AP 763 can be an Xn applicationprotocol layer (XnAP or Xn-AP) 763 for the Xn interface 112 that isdefined between two or more RAN nodes 111.

The NG-AP 763 can support the functions of the NG interface 113 and caninclude Elementary Procedures (EPs). An NG-AP EP can be a unit ofinteraction between the NG-RAN node 111 and the AMF 321. The NG-AP 763services can include two groups: UE-associated services (e.g., servicesrelated to a UE 101) and non-UE-associated services (e.g., servicesrelated to the whole NG interface instance between the NG-RAN node 111and AMF 321). These services can include functions including, but notlimited to: a paging function for the sending of paging requests toNG-RAN nodes 111 involved in a particular paging area; a UE contextmanagement function for allowing the AMF 321 to establish, modify,and/or release a UE context in the AMF 321 and the NG-RAN node 111; amobility function for UEs 101 in ECM-CONNECTED mode for intra-system HOsto support mobility within NG-RAN and inter-system HOs to supportmobility from/to EPS systems; a NAS Signaling Transport function fortransporting or rerouting NAS messages between UE 101 and AMF 321; a NASnode selection function for determining an association between the AMF321 and the UE 101; NG interface management function(s) for setting upthe NG interface and monitoring for errors over the NG interface; awarning message transmission function for providing means to transferwarning messages via NG interface or cancel ongoing broadcast of warningmessages; a Configuration Transfer function for requesting andtransferring of RAN configuration information (e.g., SON information,performance measurement (PM) data, etc.) between two RAN nodes 111 viaCN 120; and/or other like functions.

The XnAP 763 can support the functions of the Xn interface 112 and caninclude XnAP basic mobility procedures and XnAP global procedures. TheXnAP basic mobility procedures can include procedures used to handle UEmobility within the NG RAN 111 (or E-UTRAN 210), such as handoverpreparation and cancellation procedures, SN Status Transfer procedures,UE context retrieval and UE context release procedures, RAN pagingprocedures, dual connectivity related procedures, and the like. The XnAPglobal procedures can include procedures that are not related to aspecific UE 101, such as Xn interface setup and reset procedures, NG-RANupdate procedures, cell activation procedures, and the like.

In LTE implementations, the AP 763 can be an S1 Application Protocollayer (S1-AP) 763 for the S1 interface 113 defined between an E-UTRANnode 111 and an MME, or the AP 763 can be an X2 application protocollayer (X2AP or X2-AP) 763 for the X2 interface 112 that is definedbetween two or more E-UTRAN nodes 111.

The S1 Application Protocol layer (S1-AP) 763 can support the functionsof the S1 interface, and similar to the NG-AP discussed previously, theS1-AP can include S1-AP EPs. An S1-AP EP can be a unit of interactionbetween the E-UTRAN node 111 and an MME 221 within an LTE CN 120. TheS1-AP 763 services can include two groups: UE-associated services andnon UE-associated services. These services perform functions including,but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UEcapability indication, mobility, NAS signaling transport, RANInformation Management (RIM), and configuration transfer.

The X2AP 763 can support the functions of the X2 interface 112 and caninclude X2AP basic mobility procedures and X2AP global procedures. TheX2AP basic mobility procedures can include procedures used to handle UEmobility within the E-UTRAN 120, such as handover preparation andcancellation procedures, SN Status Transfer procedures, UE contextretrieval and UE context release procedures, RAN paging procedures, dualconnectivity related procedures, and the like. The X2AP globalprocedures can include procedures that are not related to a specific UE101, such as X2 interface setup and reset procedures, load indicationprocedures, error indication procedures, cell activation procedures, andthe like.

The SCTP layer (alternatively referred to as the SCTP/IP layer) 762 canprovide guaranteed delivery of application layer messages (e.g., NGAP orXnAP messages in NR implementations, or S1-AP or X2AP messages in LTEimplementations). The SCTP 762 can ensure reliable delivery of signalingmessages between the RAN node 111 and the AMF 321/MME 221 based, inpart, on the IP protocol, supported by the IP 761. The Internet Protocollayer (IP) 761 can be used to perform packet addressing and routingfunctionality. In some implementations the IP layer 761 can usepoint-to-point transmission to deliver and convey PDUs. In this regard,the RAN node 111 can include L2 and L1 layer communication links (e.g.,wired or wireless) with the MME/AMF to exchange information.

In a second example, a user plane protocol stack can include, in orderfrom highest layer to lowest layer, SDAP 747, PDCP 740, RLC 730, MAC720, and PHY 710. The user plane protocol stack can be used forcommunication between the UE 101, the RAN node 111, and UPF 302 in NRimplementations or an S-GW 222 and P-GW 223 in LTE implementations. Inthis example, upper layers 751 can be built on top of the SDAP 747, andcan include a user datagram protocol (UDP) and IP security layer(UDP/IP) 752, a General Packet Radio Service (GPRS) Tunneling Protocolfor the user plane layer (GTP-U) 753, and a User Plane PDU layer (UPPDU) 763.

The transport network layer 754 (also referred to as a “transportlayer”) can be built on IP transport, and the GTP-U 753 can be used ontop of the UDP/IP layer 752 (including a UDP layer and IP layer) tocarry user plane PDUs (UP-PDUs). The IP layer (also referred to as the“Internet layer”) can be used to perform packet addressing and routingfunctionality. The IP layer can assign IP addresses to user data packetsin any of IPv4, IPv6, or PPP formats, for example.

The GTP-U 753 can be used for carrying user data within the GPRS corenetwork and between the radio access network and the core network. Theuser data transported can be packets in any of IPv4, IPv6, or PPPformats, for example. The UDP/IP 752 can provide checksums for dataintegrity, port numbers for addressing different functions at the sourceand destination, and encryption and authentication on the selected dataflows. The RAN node 111 and the S-GW 222 can utilize an S1-U interfaceto exchange user plane data via a protocol stack including an L1 layer(e.g., PHY 710), an L2 layer (e.g., MAC 720, RLC 730, PDCP 740, and/orSDAP 747), the UDP/IP layer 752, and the GTP-U 753. The S-GW 222 and theP-GW 223 can utilize an S5/S8a interface to exchange user plane data viaa protocol stack including an L1 layer, an L2 layer, the UDP/IP layer752, and the GTP-U 753. As discussed previously, NAS protocols cansupport the mobility of the UE 101 and the session management proceduresto establish and maintain IP connectivity between the UE 101 and theP-GW 223.

Moreover, although not shown by FIG. 7, an application layer can bepresent above the AP 763 and/or the transport network layer 754. Theapplication layer can be a layer in which a user of the UE 101, RAN node111, or other network element interacts with software applications beingexecuted, for example, by application circuitry 405 or applicationcircuitry 505, respectively. The application layer can also provide oneor more interfaces for software applications to interact withcommunications systems of the UE 101 or RAN node 111, such as thebaseband circuitry 610. In some implementations the IP layer and/or theapplication layer can provide the same or similar functionality aslayers 5-7, or portions thereof, of the Open Systems Interconnection(OSI) model (e.g., OSI Layer 7—the application layer, OSI Layer 6—thepresentation layer, and OSI Layer 5—the session layer).

FIG. 8 illustrates components of a core network in accordance with oneor more implementations. The components of the CN 220 can be implementedin one physical node or separate physical nodes including components toread and execute instructions from a machine-readable orcomputer-readable medium (e.g., a non-transitory machine-readablestorage medium). In implementations, the components of CN 320 can beimplemented in a same or similar manner as discussed herein with regardto the components of CN 220. In some implementations, NFV is utilized tovirtualize any or all of the above-described network node functions viaexecutable instructions stored in one or more computer-readable storagemediums (described in further detail below). A logical instantiation ofthe CN 220 can be referred to as a network slice 801, and individuallogical instantiations of the CN 220 can provide specific networkcapabilities and network characteristics. A logical instantiation of aportion of the CN 220 can be referred to as a network sub-slice 802(e.g., the network sub-slice 802 is shown to include the P-GW 223 andthe PCRF 226).

As used herein, the terms “instantiate,” “instantiation,” and the likecan refer to the creation of an instance, and an “instance” can refer toa concrete occurrence of an object, which can occur, for example, duringexecution of program code. A network instance can refer to informationidentifying a domain, which can be used for traffic detection androuting in case of different IP domains or overlapping IP addresses. Anetwork slice instance can refer to a set of network functions (NFs)instances and the resources (e.g., compute, storage, and networkingresources) required to deploy the network slice.

With respect to 5G systems (see, e.g., FIG. 3), a network slice alwaysincludes a RAN part and a CN part. The support of network slicing relieson the principle that traffic for different slices is handled bydifferent PDU sessions. The network can realize the different networkslices by scheduling and also by providing different L1/L2configurations. The UE 301 provides assistance information for networkslice selection in an appropriate RRC message, if it has been providedby NAS. While the network can support large number of slices, the UEneed not support more than 8 slices simultaneously.

A network slice can include the CN 320 control plane and user plane NFs,NG-RANs 310 in a serving PLMN, and a N3IWF functions in the servingPLMN. Individual network slices can have different S-NSSAI and/or canhave different SSTs. NSSAI includes one or more S-NSSAIs, and eachnetwork slice is uniquely identified by an S-NSSAI. Network slices candiffer for supported features and network functions optimizations,and/or multiple network slice instances can deliver the sameservice/features but for different groups of UEs 301 (e.g., enterpriseusers). For example, individual network slices can deliver differentcommitted service(s) and/or can be dedicated to a particular customer orenterprise. In this example, each network slice can have differentS-NSSAIs with the same SST but with different slice differentiators.Additionally, a single UE can be served with one or more network sliceinstances simultaneously via a 5G AN and associated with eight differentS-NSSAIs. Moreover, an AMF 321 instance serving an individual UE 301 canbelong to each of the network slice instances serving that UE.

Network Slicing in the NG-RAN 310 involves RAN slice awareness. RANslice awareness includes differentiated handling of traffic fordifferent network slices, which have been pre-configured. Sliceawareness in the NG-RAN 310 is introduced at the PDU session level byindicating the S-NSSAI corresponding to a PDU session in all signalingthat includes PDU session resource information. How the NG-RAN 310supports the slice enabling in terms of NG-RAN functions (e.g., the setof network functions that include each slice) is implementationdependent. The NG-RAN 310 selects the RAN part of the network sliceusing assistance information provided by the UE 301 or the 5GC 320,which unambiguously identifies one or more of the pre-configured networkslices in the PLMN. The NG-RAN 310 also supports resource management andpolicy enforcement between slices as per SLAs. A single NG-RAN node cansupport multiple slices, and the NG-RAN 310 can also apply anappropriate RRM policy for the SLA in place to each supported slice. TheNG-RAN 310 can also support QoS differentiation within a slice.

The NG-RAN 310 can also use the UE assistance information for theselection of an AMF 321 during an initial attach, if available. TheNG-RAN 310 uses the assistance information for routing the initial NASto an AMF 321. If the NG-RAN 310 is unable to select an AMF 321 usingthe assistance information, or the UE 301 does not provide any suchinformation, the NG-RAN 310 sends the NAS signaling to a default AMF321, which can be among a pool of AMFs 321. For subsequent accesses, theUE 301 provides a temp ID, which is assigned to the UE 301 by the 5GC320, to enable the NG-RAN 310 to route the NAS message to theappropriate AMF 321 as long as the temp ID is valid. The NG-RAN 310 isaware of, and can reach, the AMF 321 that is associated with the tempID. Otherwise, the method for initial attach applies.

The NG-RAN 310 supports resource isolation between slices. NG-RAN 310resource isolation can be achieved by means of RRM policies andprotection mechanisms that should avoid that shortage of sharedresources if one slice breaks the service level agreement for anotherslice. In some implementations, it is possible to fully dedicate NG-RAN310 resources to a certain slice. How NG-RAN 310 supports resourceisolation is implementation dependent.

Some slices can be available only in part of the network. Awareness inthe NG-RAN 310 of the slices supported in the cells of its neighbors canbe beneficial for inter-frequency mobility in connected mode. The sliceavailability does not change within the UE's registration area. TheNG-RAN 310 and the 5GC 320 are responsible to handle a service requestfor a slice that is or is not available in a given area. Admission orrejection of access to a slice can depend on factors such as support forthe slice, availability of resources, support of the requested serviceby NG-RAN 310.

The UE 301 can be associated with multiple network slicessimultaneously. In case the UE 301 is associated with multiple slicessimultaneously, only one signaling connection is maintained, and forintra-frequency cell reselection, the UE 301 tries to camp on the bestcell. For inter-frequency cell reselection, dedicated priorities cancontrol the frequency on which the UE 301 camps. The 5GC 320 is tovalidate that the UE 301 has the rights to access a network slice. Priorto receiving an Initial Context Setup Request message, the NG-RAN 310can be allowed to apply some provisional/local policies, based onawareness of a particular slice that the UE 301 is requesting to access.During the initial context setup, the NG-RAN 310 is informed of theslice for which resources are being requested.

NFV architectures and infrastructures can be used to virtualize one ormore NFs, alternatively performed by proprietary hardware, onto physicalresources including a combination of industry-standard server hardware,storage hardware, or switches. In other words, NFV systems can executevirtual or reconfigurable implementations of one or more EPCcomponents/functions.

FIG. 9 is a block diagram illustrating components, according to someexample implementations, of a system 900 to support NFV. The system 900is illustrated as including a VIM 902, an NFVI 904, an VNFM 906, VNFs908, an EM 910, an NFVO 912, and a NM 914.

The VIM 902 manages the resources of the NFVI 904. The NFVI 904 caninclude physical or virtual resources and applications (includinghypervisors) used to execute the system 900. The VIM 902 can manage thelife cycle of virtual resources with the NFVI 904 (e.g., creation,maintenance, and tear down of VMs associated with one or more physicalresources), track VM instances, track performance, fault and security ofVM instances and associated physical resources, and expose VM instancesand associated physical resources to other management systems.

The VNFM 906 can manage the VNFs 908. The VNFs 908 can be used toexecute EPC components/functions. The VNFM 906 can manage the life cycleof the VNFs 908 and track performance, fault and security of the virtualaspects of VNFs 908. The EM 910 can track the performance, fault andsecurity of the functional aspects of VNFs 908. The tracking data fromthe VNFM 906 and the EM 910 can include, for example, PM data used bythe VIM 902 or the NFVI 904. Both the VNFM 906 and the EM 910 can scaleup/down the quantity of VNFs of the system 900.

The NFVO 912 can coordinate, authorize, release and engage resources ofthe NFVI 904 in order to provide the requested service (e.g., to executean EPC function, component, or slice). The NM 914 can provide a packageof end-user functions with the responsibility for the management of anetwork, which can include network elements with VNFs, non-virtualizednetwork functions, or both (management of the VNFs can occur via the EM910).

FIG. 10 is a block diagram illustrating components, according to someexample implementations, able to read instructions from amachine-readable or computer-readable medium (e.g., a non-transitorymachine-readable storage medium) and perform any one or more of themethodologies discussed herein. Specifically, FIG. 10 shows adiagrammatic representation of hardware resources 1000 including one ormore processors (or processor cores) 1010, one or more memory/storagedevices 1020, and one or more communication resources 1030, each ofwhich can be communicatively coupled via a bus 1040. For implementationswhere node virtualization (e.g., NFV) is utilized, a hypervisor 1002 canbe executed to provide an execution environment for one or more networkslices/sub-slices to utilize the hardware resources 1000.

The processors 1010 can include, for example, a processor 1012 and aprocessor 1014. The processor(s) 1010 can be, for example, a centralprocessing unit (CPU), a reduced instruction set computing (RISC)processor, a complex instruction set computing (CISC) processor, agraphics processing unit (GPU), a DSP such as a baseband processor, anASIC, an FPGA, a radio-frequency integrated circuit (RFIC), anotherprocessor (including those discussed herein), or any suitablecombination thereof.

The memory/storage devices 1020 can include main memory, disk storage,or any suitable combination thereof. The memory/storage devices 1020 caninclude, but are not limited to, any type of volatile or nonvolatilememory such as dynamic random access memory (DRAM), static random accessmemory (SRAM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), Flashmemory, solid-state storage, etc.

The communication resources 1030 can include interconnection or networkinterface components or other suitable devices to communicate with oneor more peripheral devices 1004 or one or more databases 1006 via anetwork 1008. For example, the communication resources 1030 can includewired communication components (e.g., for coupling via USB), cellularcommunication components, NFC components, Bluetooth® (or Bluetooth® LowEnergy) components, Wi-Fi® components, and other communicationcomponents.

Instructions 1050 can include software, a program, an application, anapplet, an app, or other executable code for causing at least any of theprocessors 1010 to perform any one or more of the methodologiesdiscussed herein. The instructions 1050 can reside, completely orpartially, within at least one of the processors 1010 (e.g., within theprocessor's cache memory), the memory/storage devices 1020, or anysuitable combination thereof. Furthermore, any portion of theinstructions 1050 can be transferred to the hardware resources 1000 fromany combination of the peripheral devices 1004 or the databases 1006.Accordingly, the memory of processors 1010, the memory/storage devices1020, the peripheral devices 1004, and the databases 1006 are examplesof computer-readable and machine-readable media.

FIG. 11 is a block diagram illustrating an example of radio linkmonitoring (RLM)-based unicast sidelink (SL) management, according toone or more implementations. The implementations disclosed hereinprovide methods for new radio (NR) SL communication, and RLM and radiolink failure (RLF) declaration-based access stratum (AS)-level linkmanagement. In particular, the implementations enable SL radio resourcemanagement (RRM)-based AS-level link management and RLM reference signal(RS) design in accordance with 3GPP RAN 1. Further, in accordance with3GPP RAN2, the air interface physical layer (Uu) RLM model is supportedfor SL RLM. For example, the AS-level link status (e.g., failure) iscommunicated to the upper layer by the implementations. In scenarioswhere SL radio link control (RLC) acknowledgement mode (AM) is supportedfor unicast, the triggering of RLF declarations by indication from theRLC that a maximum number of retransmissions has been reached isenabled.

In some implementations, RLM/RLF functions are enabled for unicast SLcommunications. Because generic RLM detection resources are supported,both transmitter (TX)-side and receiver (RX)-side RLM are enabled. Insome implementations, a processor for a base station includes firstcircuitry configured to generate a radio resource control (RRC) messageincluding an RRC information element indicating a number of unicast SLRLM reference signals. RLF detection criteria can be semi-staticallyconfigured using RRC signaling. In some implementations, the processorincludes second circuitry configured to encode the RRC message fortransmission to a user equipment (UE) 101. Unicast SL radio bearer/linkconnections can be released, resumed, or recovered using timeroperations. As a result, RLM/RLF and associated unicast SL management issupported by the implementations in a resource efficient manner.

In some implementations, configurable RLM resources and RLF metrics areused. For example, the resources used for RLM as well as the RLF metricscan be configured by the network using RRC signaling when the UE 101 isin a coverage range of a cellular network (e.g., mode-1). In suchimplementations, the resources used for RLM as well as the RLF metricscan be preconfigured using default parameters when the UE 101 is out ofcoverage of the network, (e.g., mode-2). In particular, the RRCinformation element (IE) “RadioLinkMonitoringV2Xconfig” can be used torealize the configuration and RadioLinkMonitoringV2XConfig IE can beincluded in the UE 101's SL-specific RRC configuration IE. Suchimplementations can be enabled as follows:

RadioLinkMonitoringV2XConfig ::= SEQUENCE {failureDetectionResourcesToAddModList SEQUENCE(SIZE(1..maxNrofFailureDetectionResourcesV2X)) OFRadioLinkMonitoringResourceV2X OPTIONAL, -- Need NfailureDetectionResourcesToReleaseList SEQUENCE(SIZE(1..maxNrofFailureDetectionResourcesV2X)) OFRadioLinkMonitoringRSV2X-Id }

In the example above, the parameter maxNrofFailureDetectionResourcesV2Xdefines a bound on a number of unicast SL RLM RS can be configured. Ifonly one RLM-Resource is configured per unicast SL, this parameterdetermines a bound on a number of unicast SLs to be configured using theRLM function. The IE RadioLinkMonitoringResourceV2X can be configured asfollows:

RadioLinkMonitoringResourceV2X ::= SEQUENCE {radioLinkMonitoringResource-Id RadioLinkMonitoringResourceV2X-Id,detectionResource CHOICE { csi-RS-V2X-Index NZP-CSI-RS-V2X-ResourceId,DMRS RLC-NACK HARQ-NACK }, rlf-TimersAndConstantsV2X SetupRelease {RLF-TimersAndConstantsV2X } OPTIONAL, -- Need MrlmInSyncOutOfSyncThreshold  ENUMERATED {n1} OPTIONAL, -- Need S . . . }

In the example above, the radioLinkMonitoringResource-Id parameterdefines the ID of the unicast SL RLM-resource. In some implementations,the RRC information element further indicates a type of the RLMresource. For example, the detectionResource parameter defines the typeof RLM resources. In some implementations, the generated referencesignal is a channel state information-reference signal (CSI-RS) or ademodulation reference signal (DMRS). In particular, the channel stateinformation-reference signal (CSI-RS) and the demodulation referencesignal (DMRS) can be configured for RLF detection at the RX side.RLC-NACK and HARQ-NACK, defining the RLC failure and PHY HACK-NACK,respectively, can be configured for RLF detection at the TX side. Insome implementations, the RRC information element further indicates atimer and a constant for at least one of a radio link failure (RLF)detection procedure or a unicast SL connection procedure. For example,the configuration of rfl-TimersAndConstantsV2X defines the timers andconstants used for RLF detection and unicast SL connection procedures.In some implementations, the RRC information element further indicatesan IS/OOS threshold configuration based on the IS threshold and the OOSthreshold for the RLM resource. For example, therlmInSyncOutOfSyncThreshold parameter defines the IS/OOS thresholdconfigurations. In some implementations, a processor for a base stationincludes third circuitry configured to generate a reference signalindicating an in-sync (IS) threshold and an out-of-sync (OOS) thresholdfor an RLM resource. Different thresholds can be enabled for IS/OOSswitching and the associated SL procedure operations. In someimplementations, the processor includes fourth circuitry configured toencode the reference signal for transmission to the UE 101. Theprocessor includes fifth circuitry configured to transmit the RRCmessage and the reference signal to the UE 101.

In some implementations, in-synch (IS)/out-of-sync (OOS) determinationis performed using the RLM resources. For example, an IS/OOS status isdetermined based on the configured RLM resource, i.e., detectionResourceusing RadioLinkMonitoringResourceV2X. In particular, when a referencesignal (RS), such as CSI-RS or DMRS, is configured as the RLM resource,an estimated block error rate (BLER) can be used for IS/OOSdetermination. For other RLM resources, e.g., radio link controlnegative acknowledgement (RLC-NACK) or hybrid automatic repeat requestNACK (HARQ-NACK), the thresholds of IS and OOS can be semi-staticallyconfigured using RLF-TimersAndConstantsV2X as follows:

RLF-TimersAndConstantsV2X::= SEQUENCE { t310-V2X ENUMERATED {ms0, ms50,ms100, ms200, ms500, ms1000, ms2000, ms4000, ms6000}, n310 ENUMERATED{n1, n2, n3, n4, n6, n8, n10, n20}, n311 ENUMERATED {n1, n2, n3, n4, n5,n6, n8, n10}, t311-V2X ENUMERATED {ms1000, ms3000, ms5000, ms1000,ms15000, ms20000, ms30000} nIS ENUMERATED {n1, n2, n3, n4, n6, n8, n10 }OPTIONAL, nOOS ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n20}OPTIONAL, . . . }

In some implementations, the reference signal further indicates a numberof consecutive reception events for an IS determination. In the exampleabove, the nIS parameter defines a number of consecutive receptionevents for determining the IS state. In particular, if detectionResourceis set to RLC-NACK (HARQ-NACK), the nIS parameter indicates a number ofconsecutive RLC-ACK (HARQ-ACK) for being in the IS state. In someimplementations, the reference signal further indicates a number ofconsecutive erroneous reception events required for an OOSdetermination. The nOOS parameter defines a number of consecutiveerroneous reception events for determining the OOS state. In particular,if detectionResource is set to RLC-NACK (HARQ-NACK), nOOS indicates thenumber of consecutive RLC-NACK (HARQ-NACK) for being in the OOS state.The n3xy parameter is defined in TS 38.331. T3xy-V2X are timers definedto control RLC processes, as illustrated and described below withreference to FIGS. 11 and 12.

In some implementations, a radio bearer (RB)-specific RLM configurationis used. In such implementations, the unicast SL RLM configuration(RadioLinkMonitoringV2Xconfig) is configured in an RB-specific manner,such that RLM-related functions can be performed at the RB-level. Inparticular, RadioLinkMonitoringV2XConfig can be configured usingRLC-BearerV2XConfig as follows:

RLC-BearerV2XConfig ::= SEQUENCE { logicalChannelIdentityLogicalChannelIdentity, servedRadioBearer CHOICE { srb-IdentitySRB-Identity, drb-Identity DRB-Identity } OPTIONAL, -- CondLCH-SetupOnly reestablishRLC ENUMERATED {true} OPTIONAL, -- Need Nrlc-Config RLC-Config OPTIONAL, -- Cond LCH-Setupmac-LogicalChannelConfig LogicalChannelConfig OPTIONAL, -- CondLCH-Setup rlmV2XConfig  RadioLinkMonitoringV2Xconfig .   . . }

Depending on how the RLF timers are configured, at least two differentimplementations can be realized for RLM-assisted unicast SL management.Referring to FIG. 11, the first implementation is based on single-timerunicast SL management. In this implementation, the T310-V2X timer isconfigured in accordance with RLF-TimersAndConstantsV2X to determine ifan RB can be released or resumed when RLF is detected for an associatedradio link. As illustrated in FIG. 11, when a number of consecutive OOSstates detected using the RLM function exceeds the constant N310, thetimer T310-V2X can be started. Meanwhile, the RLM monitors the radiolink quality. If a number of consecutive IS events exceeds the constantN311, the timer T310-V2X can be stopped and the RB associated with theRLM function can be consequently resumed. Else, the timer T310-V2X willrun until expiring. Upon the expiration of the T310-V2X timer, the RBcan be released by the UE 101. The second implementation of RLM-assistedunicast SL management is illustrated and described below in more detailwith reference to FIG. 12.

FIG. 12 is a block diagram illustrating an example of RLM-based unicastSL management with SL recovery, according to one or moreimplementations. The second implementation of RLM-assisted unicast SLmanagement, as illustrated in FIG. 12, is based on unicast SL managementusing radio link re-establishment. In this implementation, both timersT310-V2X and T311-V2X are configured in accordance withRLF-TimersAndConstantsV2X to control the unicast SL management. Inparticular, timer T310-V2X controls the release or resumption of the RBlink while timer T311-V2X controls the recovery of the RB radio. In thismanner, both the timers T310-V2X and T311-V2X are configured usingRLF-TimersAndConstantsV2X to control the RLM, i.e., the manner in whichan RB can be released, resumed, or recovered when RLF is detected forthe radio link. Hence, the timer T310-V2X controls the release orresumption of the RB link while the timer T311-V2X controls the recoveryof the RB radio.

As illustrated in FIG. 12, the two timers can be operated as in thefollowing description. For the timer T310-V2X, when a number ofconsecutive OOS states detected by the RLM function exceeds the constantN310, the timer T310-V2X can be started. Meanwhile, RLM is used tomonitor the radio link quality. If a number of consecutive IS eventsexceeds the constant N311, the timer T310-V2X can be stopped and theassociated RB can be resumed. Else, the timer T310-V2X will run untilexpiry. Upon the expiration of T310-V2X, the RB can be released by theUE 101. For the timer T311-V2X, upon the commencement of the timerT310-V2X, the unicast radio link reestablishment process can be begun,which triggers the unicast SL discovery procedure. Upon the commencementof the unicast SL discovery procedure, the timer T311-V2X can bestarted. If a higher quality unicast SL link is recovered, e.g., using anew beam, the timer T311-V2X can be stopped. If the timer T311-V2X isstopped, the SL RB link can be resumed. Else, the timer T311-V2X willrun until expiring. Upon the expiration of T311-V2X, the RB can bereleased by the UE 101.

In some implementations, an RRC message is generated that includes anRRC information element having a parameter that defines a bound on anumber of unicast SL RLM reference signals that can be configured. Insuch implementations, a base station, such as a gNB 111 or an eNB,encode the RRC message for transmission to a UE 101. In otherimplementations, the base station generates am RS including anindication of an IS threshold and an OOS threshold for an RLM resource.In such implementations, the base station further encodes the RS fortransmission to the UE 101. The implementations disclosed herein enableRLM/RLF functions for unicast SL communications. Moreover, using genericRLM detection resources, both TX-side and RX-side RLM are supported, andRLF detection criteria can be semi-statically configured using RRCsignaling. The unicast SL RB link connection can be released, resumed,or recovered using timer operations. As a result, RLM/RLF and associatedunicast SL management is supported in a resource efficient manner.

FIG. 13 is a flowchart illustrating a process for RLM monitoring forunicast SL communications. In some implementations, the process of FIG.13 is performed by a processor for a base station (e.g., an eNB or a gNB111).

The processor generates (1304) a radio resource control (RRC) messageincluding an RRC information element indicating a number of unicastsidelink (SL) radio link monitoring (RLM) reference signals. RLFdetection criteria can be semi-statically configured using RRCsignaling.

The processor encodes (1308) the RRC message for transmission to theuser equipment (UE) 101. Unicast SL radio bearer/link connections can bereleased, resumed, or recovered using timer operations. As a result,RLM/RLF and associated unicast SL management is supported by theimplementations in a resource efficient manner.

The processor generates (1312) a reference signal indicating an in-sync(IS) threshold and an out-of-sync (OOS) threshold for an RLM resource.Different thresholds can be enabled for IS/OOS switching and theassociated SL procedure operations.

The processor encodes (1316) the reference signal for transmission tothe UE 101. For example, an IS/OOS status is determined based on theconfigured RLM resource, i.e., detectionResource usingRadioLinkMonitoringResourceV2X. In particular, when a reference signal(RS), such as CSI-RS or DMRS, is configured as the RLM resource, anestimated block error rate (BLER) can be used for IS/OOS determination.The processor transmits (1320) the RRC message and the reference signalto the UE 101.

For one or more implementations, at least one of the components setforth in one or more of the preceding figures can be configured toperform one or more operations, techniques, processes, and/or methods asset forth in the example section below. For example, the basebandcircuitry as described above in connection with one or more of thepreceding figures can be configured to operate in accordance with one ormore of the examples set forth below. For another example, circuitryassociated with a UE, base station, network element, etc. as describedabove in connection with one or more of the preceding figures can beconfigured to operate in accordance with one or more of the examples setforth below.

Example 1 can include a method in which the resources used for RLM aswell as the RLF metric can be configured by the network using RRCsignaling when a UE is in a coverage region of the cellular network,i.e., mode-1. The resources used for RLM as well as the RLF metric canbe preconfigured using default parameters when the UE is out of coverageof the network, i.e., mode-2.

Example 2 can include the method of Example 1 or some other exampleherein, wherein the RRC information element (IE)“RadioLinkMonitoringV2XConfig” can be used to realize the configuration.The RadioLinkMonitoringV2XConfig IE configuration can be included in theUE SL-specific RRC configuration IE as follows:

RadioLinkMonitoringV2XConfig ::= SEQUENCE {failureDetectionResourcesToAddModList SEQUENCE(SIZE(1..maxNrofFailureDetectionResourcesV2X)) OFRadioLinkMonitoringResourceV2X OPTIONAL, -- Need NfailureDetectionResourcesToReleaseList SEQUENCE(SIZE(1..maxNrofFailureDetectionResourcesV2X)) OFRadioLinkMonitoringRSV2X-Id }

Example 3 can include the parameter maxNrofFailureDetectionResourcesV2Xof Example 2 or some other example herein, wherein a bound on a numberof unicast SL RLM reference signals can be configured. If only oneRLM-Resource is configured per unicast SL, this parameter determines abound on a number of unicast SLs to be configured using the RLMfunction.

Example 4 can include the parameter IE RadioLinkMonitoringResourceV2X ofExample 2 or some other example herein, wherein the parameter can bedesigned as follows:

RadioLinkMonitoringResourceV2X ::= SEQUENCE {radioLinkMonitoringResource-Id RadioLinkMonitoringResourceV2X-Id,detectionResource CHOICE { csi-RS-V2X-Index NZP-CSI-RS-V2X-ResourceId,DMRS RLC-NACK HARQ-NACK }, rlf-TimersAndConstantsV2X SetupRelease {RLF-TimersAndConstantsV2X } OPTIONAL, -- Need MrlmInSyncOutOfSyncThreshold  ENUMERATED {n1} OPTIONAL, -- Need S . . . }

Example 5 can include the parameter radioLinkMonitoringResource-Id ofExample 4 or some other example herein, wherein the parameter definesthe ID of unicast SL RLM-resources.

Example 6 can include the detectionResource parameter of Example 4 todefine a type of RLM resources used. In particular, CSI-RS and DMRS canbe configured for RLF detection on the RX side. RLC-NACK and HARQ-NACK,defining the RLC failure and the physical layer (PHY) hybridacknowledgment (HACK)-NACK respectively, can be configured for RLFdetection at the TX side.

Example 7 can include the rfl-TimersAndConstantsV2X parameter of Example4 or some other example herein, wherein the parameter defines the timersand constants for RLF detection and the unicast SL connectionprocedures.

Example 8 can include the rlmInSyncOutOfSyncThreshold parameter ofExample 4 or some other example herein, wherein the parameter definesthe IS/OOS threshold configurations. This parameter allows the differentthresholds to be used for IS/OOS switching and associated SL procedureoperations.

Example 9 can include a method where the IS/OOS state is determinedbased on the configured RLM resource, i.e., the detectionResourceparameter in the RadioLinkMonitoringResourceV2X configuration.

Example 10 can include the method of Example 9 or some other exampleherein, wherein when the RS, such as CSI-RS or DMRS, is configured aspart of the RLM resources, the estimated BLER can be used for IS/OOSstate determination.

Example 11 can include the method of Example 9 or some other exampleherein, wherein for other types of RLM resources, e.g., RLC-NACK orHARQ-NACK, the thresholds of IS and OOS can be semi-staticallyconfigured using RLF-TimersAndConstantsV2X as follows:

RLF-TimersAndConstantsV2X::= SEQUENCE { t310-V2X ENUMERATED {ms0, ms50,ms100, ms200, ms500, ms1000, ms2000, ms4000, ms6000}, n310 ENUMERATED{n1, n2, n3, n4, n6, n8, n10, n20}, n311 ENUMERATED {n1, n2, n3, n4, n5,n6, n8, n10}, t311-V2X ENUMERATED {ms1000, ms3000, ms5000, ms10000,ms15000, ms20000, ms30000} nIS ENUMERATED {n1, n2, n3, n4, n6, n8, n10 }OPTIONAL, nOOS ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n20}OPTIONAL, . . . }

Example 12 can include the nIS parameter of Example 11 or some otherexample herein, wherein the parameter defines a number of consecutivesuccessful reception events for the determination of the IS state. Inparticular, if detectionResource is set to RLC-NACK (HARQ-NACK), nISindicates the number of consecutive RLC-ACK (HARQ-ACK) for being in theIS state.

Example 13 can include the nOOS parameter of Example 11 or some otherexample herein, wherein the parameter defines the number of consecutiveerroneous reception events for the determination of the OOS state. Inparticular, if detectionResource is set to RLC-NACK (HARQ-NACK), nOOSindicates the number of consecutive RLC-NACK (HARQ-NACK) for being inthe OOS state.

Example 14 can include the n3xy parameter as defined in TS 38.331.T3xy-V2X are timers defined to control various RLC processes.

Example 15 can include the unicast SL RLM configuration parameterRadioLinkMonitoringV2XConfig of Example 1. This is configured in anRB-specific manner, such that RLM-related functions can be performed atthe RB level. In particular, the RadioLinkMonitoringV2XConfig parametercan be configured using RLC-BearerV2XConfig as follows:

RLC-BearerV2XConfig ::= SEQUENCE{ logicalChannelIdentityLogicalChannelIdentity, servedRadioBearer CHOICE {  srb-IdentitySRB-Identity,  drb-Identity DRB-Identity } OPTIONAL, -- CondLCH-SetupOnly reestablishRLC ENUMERATED {true} OPTIONAL, -- Need Nrlc-Config RLC-Config OPTIONAL, -- Cond LCH-Setupmac-LogicalChannelConfig LogicalChannelConfig OPTIONAL, -- CondLCH-Setup rlmV2XConfig  RadioLinkMonitoringV2Xconfig . . . }

Example 16 can include the timer T310-V2X of Example 11 or some otherexample herein, wherein the timer is configured usingRLF-TimersAndConstantsV2X to determine whether an RB can be released orresumed when RLF is detected for the associated radio link.

Example 17 can include the parameters illustrated in FIG. 11. When anumber of consecutive OOS states detected by the RLM function exceedsthe constant N310, the timer T310-V2X can be started.

Example 18 can include monitoring of the radio link quality using RLM.If the number of consecutive IS events exceeds the constant N311, thetimer T310-V2X can be stopped. The RB associated with the RLM functioncan be consequently resumed.

Example 19 can include the timer T310-V2X running until expiry. Upon theexpiration of the timer T310-V2X, the RB can be released by the UE.

Example 20 can include both timers T310-V2X and T311-V2X of Example 11or some other example herein, wherein the timers are configured usingRLF-TimersAndConstantsV2X to control the radio link management, e.g.,the manner in which an RB can be released, resumed, or recovered whenRLF is detected for the radio link.

Example 22 can include the timer T310-V2X controlling the release orresumption of the RB link while the timer T311-V2X controls the recoveryof the RB radio.

Example 23 can include the parameters as illustrated in FIG. 12. The twotimers can operate as follows. For the timer T310-V2X, when a number ofconsecutive OOS states detected by the RLM function exceeds the constantN310, the timer T310-V2X can be started. Meanwhile, the RLM monitors theradio link quality. If the number of consecutive IS events exceeds theconstant N311, the timer T310-V2X can be stopped, and the associated RBcan be consequently resumed. Else, the timer T310-V2X will run untilexpiring. Upon the expiration of the timer T310-V2X, the RB can bereleased by the UE. For the timer T311-V2X, upon commencement of thetimer T310-V2X, the unicast radio link re-establishment process can bestarted. This process triggers the unicast SL discovery procedure. Uponthe start of the unicast SL discovery procedure, the timer T311-V2X canbe started. If a better unicast SL link is recovered, e.g., through anew beam, the timer T311-V2X can be stopped. If the timer T311-V2X isstopped, the SL RB link can be resumed. Else, the timer T311-V2X willrun until expiring. Upon the expiration of the timer T311-V2X, the RBcan be released by the UE.

Example 24 includes a method including generating a radio resourcecontrol (RRC) message that includes an RRC information element having aparameter defining a bound on a number of unicast SL RLM referencesignals that can be configured. The RRC message is encoded fortransmission to a UE.

Example 25 includes the method of Example 24 or some other exampleherein, wherein the RRC information element further indicates anidentifier of a unicast SL RLM resource.

Example 26 includes the method of Example 24 or some other exampleherein, wherein the RRC information element further indicates a type ofa RLM resource.

Example 27 includes the method of Example 24 or some other exampleherein, wherein the RRC information element further indicates a timerand a constant for a radio link failure (RLF) detection procedure or aunicast SL connection procedure.

Example 28 includes the method of Example 24 or some other exampleherein, wherein the RRC information element further indicates an IS/OOSthreshold configuration.

Example 29 includes a method including generating a reference signalincluding an indication of an IS threshold and an OOS threshold for anRLM resource. The RS is encoded for transmission to a UE.

Example 30 includes the method of Example 29 or some other exampleherein, wherein the reference signal is a channel stateinformation-reference signal (CSI-RS) or a demodulation reference signal(DMRS).

Example 31 includes the method of Example 29 or some other exampleherein, wherein the reference signal further indicates a number ofconsecutive successful reception events for an IS determination.

Example 32 includes the method of example 29 or some other exampleherein, wherein the reference signal further indicates a number ofconsecutive erroneous reception events required for an OOSdetermination.

Example 33 includes the method of any one of Examples 24-32, wherein themethod is performed by a next-generation NodeB (gNB) or portion thereof.

Example 34 includes an apparatus including means to perform one or moreelements of a method described in or related to any of Examples 1-33, orany other method or process described herein.

Example 35 can include one or more non-transitory computer-readablemedia including instructions to cause an electronic device, uponexecution of the instructions by one or more processors of theelectronic device, to perform one or more elements of a method describedin or related to any of Examples 1-33, or any other method or processdescribed herein.

Example 36 can include an apparatus including logic, modules, orcircuitry to perform one or more elements of a method described in orrelated to any of Examples 1-33, or any other method or processdescribed herein.

Example 37 can include a method, technique, or process as described inor related to any of Examples 1-33, or portions or parts thereof.

Example 38 can include an apparatus including: one or more processorsand one or more computer-readable media including instructions that,when executed by the one or more processors, cause the one or moreprocessors to perform the method, techniques, or process as described inor related to any of Examples 1-33, or portions thereof.

Example 39 can include a signal as described in or related to any ofExamples 1-33, or portions or parts thereof.

Example 40 can include a datagram, packet, frame, segment, protocol dataunit (PDU), or message as described in or related to any of Examples1-33, or portions or parts thereof, or otherwise described in thepresent disclosure.

Example 41 can include a signal encoded with data as described in orrelated to any of Examples 1-33, or portions or parts thereof, orotherwise described in the present disclosure.

Example 42 can include a signal encoded with a datagram, packet, frame,segment, protocol data unit (PDU), or message as described in or relatedto any of Examples 1-33, or portions or parts thereof, or otherwisedescribed in the present disclosure.

Example 43 can include an electromagnetic signal carryingcomputer-readable instructions, wherein execution of thecomputer-readable instructions by one or more processors is to cause theone or more processors to perform the method, techniques, or process asdescribed in or related to any of Examples 1-33, or portions thereof

Example 44 can include a computer program including instructions,wherein execution of the program by a processing element is to cause theprocessing element to carry out the method, techniques, or process asdescribed in or related to any of Examples 1-33, or portions thereof

Example 45 can include a signal in a wireless network as shown anddescribed herein.

Example 46 can include a method of communicating in a wireless networkas shown and described herein.

Example 47 can include a system for providing wireless communication asshown and described herein.

Example 48 can include a device for providing wireless communication asshown and described herein.

Any of the above-described examples can be combined with any otherexample (or combination of examples), unless explicitly statedotherwise. The foregoing description of one or more implementationsprovides illustration and description, but is not intended to beexhaustive or to limit the scope of embodiments to the precise formdisclosed. Modifications and variations are possible in light of theabove teachings or can be acquired from practice of various embodiments.

The following is a glossary of terms used in this disclosure.

Memory Medium—Any of various types of non-transitory memory devices orstorage devices. The term “memory medium” is intended to include aninstallation medium, e.g., a CD-ROM, floppy disks, or tape device; acomputer system memory or random access memory such as DRAM, DDR RAM,SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash,magnetic media, e.g., a hard drive, or optical storage; registers, orother similar types of memory elements, etc. The memory medium caninclude other types of non-transitory memory as well or combinationsthereof. In addition, the memory medium can be located in a firstcomputer system in which the programs are executed, or can be located ina second different computer system which connects to the first computersystem over a network, such as the Internet. In the latter instance, thesecond computer system can provide program instructions to the firstcomputer for execution. The term “memory medium” can include two or morememory mediums which can reside in different locations, e.g., indifferent computer systems that are connected over a network. The memorymedium can store program instructions (e.g., implemented as computerprograms) that can be executed by one or more processors.

Carrier Medium—A memory medium as described above, as well as a physicaltransmission medium, such as a bus, network, and/or other physicaltransmission medium that conveys signals such as electrical,electromagnetic, or digital signals.

Programmable Hardware Element—Includes various hardware devicesincluding multiple programmable function blocks connected via aprogrammable interconnect. Examples include Field Programmable GateArrays (FPGAs), Programmable Logic Devices (PLDs), Field ProgrammableObject Arrays (FPOAs), and Complex PLDs (CPLDs). The programmablefunction blocks can range from fine grained (combinatorial logic or lookup tables) to coarse grained (arithmetic logic units or processorcores). A programmable hardware element can also be referred to as“reconfigurable logic”.

Computer System—Any of various types of computing or processing systems,including a personal computer system (PC), mainframe computer system,workstation, network appliance, Internet appliance, personal digitalassistant (PDA), television system, grid computing system, or otherdevice or combinations of devices. In general, the term “computersystem” can be broadly defined to encompass any device (or combinationof devices) having at least one processor that executes instructionsfrom a memory medium. The term “computer system” can further refer toany type interconnected electronic devices, computer devices, orcomponents thereof. Additionally, the term “computer system” and/or“system” can refer to various components of a computer that arecommunicatively coupled with one another. Furthermore, the term“computer system” and/or “system” can refer to multiple computer devicesand/or multiple computing systems that are communicatively coupled withone another and configured to share computing and/or networkingresources.

User Equipment (UE) (or “UE Device”)—Any of various types of computersystems devices which are mobile or portable and which performs wirelesscommunications. Examples of UE devices include mobile telephones orsmart phones (e.g., iPhone™, Android™-based phones), portable gamingdevices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™iPhone™), laptops, wearable devices (e.g. smart watch, smart glasses),PDAs, portable Internet devices, music players, data storage devices, orother handheld devices, etc. In general, the term “UE” or “UE device”can be broadly defined to encompass any electronic, computing, and/ortelecommunications device (or combination of devices) which is easilytransported by a user and capable of wireless communication. The term“user equipment” or “UE” can further refer to a device with radiocommunication capabilities and can describe a remote user of networkresources in a communications network. The term “user equipment” or “UE”can be considered synonymous to, and can be referred to as, client,mobile, mobile device, mobile terminal, user terminal, mobile unit,mobile station, mobile user, subscriber, user, remote station, accessagent, user agent, receiver, radio equipment, reconfigurable radioequipment, reconfigurable mobile device, etc. Furthermore, the term“user equipment” or “UE” can include any type of wireless/wired deviceor any computing device including a wireless communications interface.

Base Station—The term “Base Station” has the full breadth of itsordinary meaning, and at least includes a wireless communication stationinstalled at a fixed location and used to communicate as part of awireless telephone system or radio system.

Processing Element—The term refers to various elements or combinationsof elements that are capable of performing a function in a device, suchas a user equipment or a cellular network device. Processing elementscan include, for example: processors and associated memory, portions orcircuits of individual processor cores, entire processor cores,processor arrays, circuits such as an Application Specific IntegratedCircuit (ASIC), programmable hardware elements such as a fieldprogrammable gate array (FPGA), as well any of various combinations ofthe above.

Channel—A medium used to convey information from a sender (transmitter)to a receiver. It should be noted that since characteristics of the term“channel” can differ according to different wireless protocols, the term“channel” as used herein can be considered as being used in a mannerthat is consistent with the standard of the type of device withreference to which the term is used. In some standards, channel widthscan be variable (e.g., depending on device capability, band conditions,etc.). For example, LTE can support scalable channel bandwidths from 1.4MHz to 20 MHz. In contrast, WLAN channels can be 22 MHz wide whileBluetooth channels can be 1 MHz wide. Other protocols and standards caninclude different definitions of channels. Furthermore, some standardscan define and use multiple types of channels, e.g., different channelsfor uplink or downlink and/or different channels for different uses suchas data, control information, etc. The term “channel” can further referto any transmission medium, either tangible or intangible, which is usedto communicate data or a data stream. The term “channel” can besynonymous with and/or equivalent to “communications channel,” “datacommunications channel,” “transmission channel,” “data transmissionchannel,” “access channel,” “data access channel,” “link,” “data link,”“carrier,” “radiofrequency carrier,” and/or any other like term denotinga pathway or medium through which data is communicated. Additionally,the term “link” as used herein refers to a connection between twodevices through a RAT for the purpose of transmitting and receivinginformation.

Band—The term “band” has the full breadth of its ordinary meaning, andat least includes a section of spectrum (e.g., radio frequency spectrum)in which channels are used or set aside for the same purpose.

Circuitry—The term “circuitry” as used herein refers to, is part of, orincludes hardware components such as an electronic circuit, a logiccircuit, a processor (shared, dedicated, or group) and/or memory(shared, dedicated, or group), an Application Specific IntegratedCircuit (ASIC), a field-programmable device (FPD) (e.g., afield-programmable gate array (FPGA), a programmable logic device (PLD),a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, ora programmable SoC), digital signal processors (DSPs), etc., that areconfigured to provide the described functionality. In someimplementations, the circuitry can execute one or more software orfirmware programs to provide at least some of the describedfunctionality. The term “circuitry” can also refer to a combination ofone or more hardware elements (or a combination of circuits used in anelectrical or electronic system) with the program code used to carry outthe functionality of that program code. In these implementations, thecombination of hardware elements and program code can be referred to asa particular type of circuitry.

Processor Circuitry—The term “processor circuitry” as used herein refersto, is part of, or includes circuitry capable of sequentially andautomatically carrying out a sequence of arithmetic or logicaloperations, or recording, storing, and/or transferring digital data. Theterm “processor circuitry” can refer to one or more applicationprocessors, one or more baseband processors, a physical centralprocessing unit (CPU), a single-core processor, a dual-core processor, atriple-core processor, a quad-core processor, and/or any other devicecapable of executing or otherwise operating computer-executableinstructions, such as program code, software modules, and/or functionalprocesses. The terms “application circuitry” and/or “baseband circuitry”can be considered synonymous to, and can be referred to as, “processorcircuitry.”

Interface Circuitry—The term “interface circuitry” as used herein refersto, is part of, or includes circuitry that enables the exchange ofinformation between two or more components or devices. The term“interface circuitry” can refer to one or more hardware interfaces, forexample, buses, I/O interfaces, peripheral component interfaces, networkinterface cards, and/or the like.

Network Element—The term “network element” as used herein refers tophysical or virtualized equipment and/or infrastructure used to providewired or wireless communication network services. The term “networkelement” can be considered synonymous to and/or referred to as anetworked computer, networking hardware, network equipment, networknode, router, switch, hub, bridge, radio network controller, RAN device,RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.

Appliance—The term “appliance,” “computer appliance,” or the like, asused herein refers to a computer device or computer system with programcode (e.g., software or firmware) that is specifically designed toprovide a specific computing resource. A “virtual appliance” is avirtual machine image to be implemented by a hypervisor-equipped devicethat virtualizes or emulates a computer appliance or otherwise isdedicated to provide a specific computing resource.

Resource—The term “resource” as used herein refers to a physical orvirtual device, a physical or virtual component within a computingenvironment, and/or a physical or virtual component within a particulardevice, such as computer devices, mechanical devices, memory space,processor/CPU time, processor/CPU usage, processor and acceleratorloads, hardware time or usage, electrical power, input/outputoperations, ports or network sockets, channel/link allocation,throughput, memory usage, storage, network, database and applications,workload units, and/or the like. A “hardware resource” can refer tocompute, storage, and/or network resources provided by physical hardwareelement(s). A “virtualized resource” can refer to compute, storage,and/or network resources provided by virtualization infrastructure to anapplication, device, system, etc. The term “network resource” or“communication resource” can refer to resources that are accessible bycomputer devices/systems via a communications network. The term “systemresources” can refer to any kind of shared entities to provide services,and can include computing and/or network resources. System resources canbe considered as a set of coherent functions, network data objects orservices, accessible through a server where such system resources resideon a single host or multiple hosts and are clearly identifiable.

Instantiate—The terms “instantiate,” “instantiation,” and the like asused herein refers to the creation of an instance. An “instance” alsorefers to a concrete occurrence of an object, which can occur, forexample, during execution of program code.

Coupled—The terms “coupled,” “communicatively coupled,” along withderivatives thereof are used herein. The term “coupled” can mean two ormore elements are in direct physical or electrical contact with oneanother, can mean that two or more elements indirectly contact eachother but still cooperate or interact with each other, and/or can meanthat one or more other elements are coupled or connected between theelements that are said to be coupled with each other. The term “directlycoupled” can mean that two or more elements are in direct contact withone another. The term “communicatively coupled” can mean that two ormore elements can be in contact with one another by a means ofcommunication including through a wire or other interconnect connection,through a wireless communication channel or ink, and/or the like.

Information Element—The term “information element” refers to astructural element containing one or more fields. The term “field”refers to individual contents of an information element, or a dataelement that contains content.

SMTC—The term “SMTC” refers to an SSB-based measurement timingconfiguration configured by SSB-MeasurementTimingConfiguration.

SSB—The term “SSB” refers to an SS/PBCH block.

Primary Cell—The term “a “Primary Cell” refers to the MCG cell,operating on the primary frequency, in which the UE either performs theinitial connection establishment procedure or initiates the connectionre-establishment procedure.

Primary SCG Cell—The term “Primary SCG Cell” refers to the SCG cell inwhich the UE performs random access when performing the Reconfigurationwith Sync procedure for DC operation.

Secondary Cell—The term “Secondary Cell” refers to a cell providingadditional radio resources on top of a Special Cell for a UE configuredwith CA.

Secondary Cell Group—The term “Secondary Cell Group” refers to thesubset of serving cells including the PSCell and zero or more secondarycells for a UE configured with DC.

Serving Cell—The term “Serving Cell” refers to the primary cell for a UEin RRC_CONNECTED not configured with CA/DC there is only one servingcell including of the primary cell. The term “serving cell” or “servingcells” can further refer to the set of cells including the SpecialCell(s) and all secondary cells for a UE in RRC_CONNECTED configuredwith CA.

Special Cell—The term “Special Cell” refers to the PCell of the MCG orthe PSCell of the SCG for DC operation; otherwise, the term “SpecialCell” refers to the Pcell.

Automatically—Refers to an action or operation performed by a computersystem (e.g., software executed by the computer system) or device (e.g.,circuitry, programmable hardware elements, ASICs, etc.), without userinput directly specifying or performing the action or operation. Thusthe term “automatically” is in contrast to an operation being manuallyperformed or specified by the user, where the user provides input todirectly perform the operation. An automatic procedure can be initiatedby input provided by the user, but the subsequent actions that areperformed “automatically” are not specified by the user, i.e., are notperformed “manually”, where the user specifies each action to perform.For example, a user filling out an electronic form by selecting eachfield and providing input specifying information (e.g., by typinginformation, selecting check boxes, radio selections, etc.) is fillingout the form manually, even though the computer system must update theform in response to the user actions. The form can be automaticallyfilled out by the computer system where the computer system (e.g.,software executing on the computer system) analyzes the fields of theform and fills in the form without any user input specifying the answersto the fields. As indicated above, the user can invoke the automaticfilling of the form, but is not involved in the actual filling of theform (e.g., the user is not manually specifying answers to fields butrather they are being automatically completed). The presentspecification provides various examples of operations beingautomatically performed in response to actions the user has taken.

Approximately—Refers to a value that is almost correct or exact. Forexample, approximately can refer to a value that is within 1 to 10percent of the exact (or desired) value. It should be noted, however,that the actual threshold value (or tolerance) can be applicationdependent. For example, in some implementations, “approximately” canmean within 0.1% of some specified or desired value, while in variousother implementations, the threshold can be, for example, 2%, 3%, 5%,and so forth, as desired or as required by the particular application.

Concurrent—Refers to parallel execution or performance, where tasks,processes, or programs are performed in an at least partiallyoverlapping manner. For example, concurrency can be implemented using“strong” or strict parallelism, where tasks are performed (at leastpartially) in parallel on respective computational elements, or using“weak parallelism”, where the tasks are performed in an interleavedmanner, e.g., by time multiplexing of execution threads.

Various components can be described as “configured to” perform a task ortasks. In such contexts, “configured to” is a broad recitation generallymeaning “having structure that” performs the task or tasks duringoperation. As such, the component can be configured to perform the taskeven when the component is not currently performing that task (e.g., aset of electrical conductors can be configured to electrically connect amodule to another module, even when the two modules are not connected).In some contexts, “configured to” can be a broad recitation of structuregenerally meaning “having circuitry that” performs the task or tasksduring operation. As such, the component can be configured to performthe task even when the component is not currently on. In general, thecircuitry that forms the structure corresponding to “configured to” caninclude hardware circuits.

Various components can be described as performing a task or tasks, forconvenience in the description. Such descriptions should be interpretedas including the phrase “configured to.” Reciting a component that isconfigured to perform one or more tasks is expressly intended not toinvoke 35 U.S.C. § 112(f) interpretation for that component.

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handledso as to reduce risks of unintentional or unauthorized access or use,and the nature of authorized use should be clearly indicated to users.

In the foregoing description, implementations of the invention have beendescribed with reference to numerous specific details that can vary fromimplementation to implementation. The description and drawings are,accordingly, to be regarded in an illustrative rather than a restrictivesense. Any definitions expressly set forth herein for terms contained insuch claims shall govern the meaning of such terms as used in theclaims.

What is claimed is:
 1. A processor for a base station, the processorincluding: protocol processing circuitry configured to: generate a radioresource control (RRC) message comprising an RRC information elementindicating (i) a number of reference signals for unicast sidelink (SL)radio link monitoring (RLM) and (ii) parameters for use with theindicated reference signals for unicast SL RLM, the parameterscorresponding to in-sync/out-of-sync (IS/OOS) switching; encode the RRCmessage for transmission to a user equipment (UE); generate a referencesignal of the indicated number of reference signals for use as an RLMresource, wherein the reference signal indicates a subset of theparameters selectable to determine a threshold for the (IS/OOS)switching; encode the reference signal for transmission to the UE; andprovide, to a radio frequency circuitry coupled to the processor, theRRC message and the reference signal for transmission to the UE.
 2. Theprocessor of claim 1, wherein the RRC information element furtherindicates a type of the RLM resource.
 3. The processor of claim 1,wherein the RRC information element further indicates a timer and aconstant for at least one of a radio link failure (RLF) detectionprocedure or a unicast SL connection procedure.
 4. The processor ofclaim 1, wherein the reference signal is a channel stateinformation-reference signal (CSI-RS) or a demodulation reference signal(DMRS).
 5. The processor of claim 1, wherein the reference signalfurther indicates a number of consecutive reception events for an ISdetermination.
 6. The processor of claim 1, wherein the reference signalfurther indicates a number of consecutive erroneous reception eventsrequired for an OOS determination.
 7. A non-transitory computer-readablestorage medium storing computer instructions, which when executed by aprocessor for a base station, cause the processor to: generate a radioresource control (RRC) message comprising an RRC information elementindicating (i) a number of reference signals for unicast sidelink (SL)radio link monitoring (RLM) and (ii) parameters for use with theindicated reference signals for unicast SL RLM, the parameterscorresponding to in-sync/out-of-sync (IS/OOS) switching; encode the RRCmessage for transmission to a user equipment (UE); generate a referencesignal of the indicated number of reference signals for use as an RLMresource, wherein the reference signal indicates a subset of theparameters selectable to determine a threshold for the (IS/OOS)switching; encode the reference signal for transmission to the UE; andtransmit the RRC message and the reference signal to the UE.
 8. Thenon-transitory computer-readable storage medium of claim 7, wherein theRRC information element further indicates a type of the RLM resource. 9.The non-transitory computer-readable storage medium of claim 7, whereinthe RRC information element further indicates a timer and a constant forat least one of a radio link failure (RLF) detection procedure or aunicast SL connection procedure.
 10. The non-transitorycomputer-readable storage medium of claim 7, wherein the referencesignal is a channel state information-reference signal (CSI-RS) or ademodulation reference signal (DMRS).
 11. The non-transitorycomputer-readable storage medium of claim 9, wherein the referencesignal further indicates a number of consecutive reception events for anIS determination.
 12. The non-transitory computer-readable storagemedium of claim 9, wherein the reference signal further indicates anumber of consecutive erroneous reception events required for an OOSdetermination.
 13. A method including: generating, by a processor for abase station, a radio resource control (RRC) message comprising an RRCinformation element indicating (i) a number of reference signals forunicast sidelink (SL) radio link monitoring (RLM) and (ii) parametersfor use with the indicated reference signals for unicast SL RLM, theparameters corresponding to in-sync/out-of-sync (IS/OOS) switching;encoding, by the processor, the RRC message for transmission to a userequipment (UE); generating, by the processor, a reference signal of theindicated number of reference signals for use as an RLM resource,wherein the reference signal indicates a subset of the parametersselectable to determine a threshold for the (IS/OOS) switching;encoding, by the processor, the reference signal for transmission to theUE; and transmitting, by the processor, the RRC message and thereference signal to the UE.
 14. The method of claim 13, wherein the RRCinformation element further indicates a type of the RLM resource. 15.The method of claim 13, wherein the RRC information element furtherindicates a timer and a constant for at least one of a radio linkfailure (RLF) detection procedure or a unicast SL connection procedure.16. The method of claim 13, wherein the reference signal is a channelstate information-reference signal (CSI-RS) or a demodulation referencesignal (DMRS).
 17. The method of claim 13, wherein the reference signalfurther indicates a number of consecutive reception events for an ISdetermination.
 18. The method of claim 13, wherein the reference signalfurther indicates a number of consecutive erroneous reception eventsrequired for an OOS determination.